AI Tools
TrustPin ships three Agent Skills that teach AI coding agents to integrate and review TrustPin certificate pinning and app attestation in iOS, macOS, Android, Flutter, and React Native apps (bare and Expo), to verify attestation tokens in your API, and to keep pins current in CI/CD, including automatic pinning when an AWS ACM certificate renews.
| Skill | Use it to |
|---|---|
trustpin-integration | Add the SDK to an app, review an existing integration, diagnose pinning errors |
trustpin-attestation | Add app attestation to an app, verify its tokens in your API or gateway, review an integration, diagnose attestation errors, keep the policy in your repository |
trustpin-cicd | Automate pin rotation and release checks with the TrustPin CLI in a pipeline or on AWS |
Once installed, ask your agent:
- “Integrate TrustPin into this app.”
- “Review our TrustPin integration.”
- “Requests fail with PINS_MISMATCH, what do I do?”
- “Automate pin rotation in CI.”
- “Pin automatically when our ACM certificate renews.”
- “Add TrustPin app attestation and verify the header in our API.”
Your agent picks the matching skill from your request. Install all three: trustpin-cicd and trustpin-attestation reuse the CLI safety rules and reference in trustpin-integration, and attestation needs pinning in place first. The skills are published at github.com/trustpin-cloud/ai-tools .
What the skills do
trustpin-integration
- Detects the platform and the HTTP client your app already uses, adds the SDK, the config file, the setup call, and wires pinning into that client.
- Lists the hosts your code connects to, so you can confirm each one is registered in your TrustPin project before shipping. In strict mode an unregistered host is refused.
- Reviews an existing integration against a checklist and diagnoses pinning errors.
trustpin-attestation
- Adds the attestation package next to pinning, at the same version, with the attestation keys in the config file pinning already reads, setup after pinning, and token binding to the user’s session.
- Makes the HTTP client your app uses carry the
TrustPin-Attestationheader, adds assertions to sensitive operations on request, and sets up debug tokens for simulators and emulators from the build, never from a file. - Writes the token check in your API (JWKS, claims, binding, debug tokens, monitor and enforce), reviews an attestation integration, and diagnoses its errors.
- Walks you through the steps that stay with you: the policy, the verifier, registering its domain, and publishing the policy with
trustpin-cli projects attestation. It never handles the verifier’s keys, secrets or debug tokens.
trustpin-cicd
- Writes the pipeline definition that keeps pins current with
trustpin-cli: a scheduled pin refresh, pinning when an AWS ACM certificate renews (EventBridge and Lambda), CodeBuild and CodePipeline jobs, a self-hosted configuration on S3 and CloudFront, and release gates. - Writes pipeline definitions for GitHub Actions, GitLab CI, Azure DevOps, Jenkins, and CircleCI, and covers mobile CI services for release checks and embedded-configuration regeneration. The DevOps guide itself shows a GitHub Actions workflow and the AWS flow.
- Keeps staging separate from signing, signs only when something changed, and puts an approval step in front of a production publish. An unattended job that signs publishes to every installed app, and the skill says so when it proposes one.
- Does not create cloud resources, deploy infrastructure, or enable a pipeline. You create the secrets, apply the infrastructure, and turn the pipeline on.
The CI/CD guidance follows the DevOps guide, including AWS ACM: Automated Certificate Pinning on Renewal.
What they do not do
- They cannot create your project, choose key management, add domains, or publish. Those steps stay with you, in the dashboard or the CLI. See Project setup.
- They cannot set up an attestation policy or run your verifier, and never handle the verifier’s keys, secrets or debug tokens. See Setting up apps and the policy.
- They never ask for your API token, master password, or private key, and they never publish a configuration without your explicit go-ahead.
- They add no MCP server, no hooks, and no background process. They are instructions and reference text, plus a script (in
trustpin-integration) that lists hostnames found in your source files. The script makes no network requests and writes no files.
Install
Claude Code
/plugin marketplace add trustpin-cloud/ai-tools
/plugin install trustpin@trustpinTo enable it for everyone on a project, commit this to the project’s .claude/settings.json:
{
"extraKnownMarketplaces": {
"trustpin": { "source": { "source": "github", "repo": "trustpin-cloud/ai-tools" } }
},
"enabledPlugins": { "trustpin@trustpin": true }
}The plugin installs all three skills. Check that they are active: type / and look for trustpin:trustpin-integration, trustpin:trustpin-attestation and trustpin:trustpin-cicd, or open /plugin and look under Installed. To update later: /plugin marketplace update trustpin.
Claude (web and desktop)
Download trustpin-integration.skill (and trustpin-attestation.skill for app attestation, trustpin-cicd.skill for CI/CD automation) from the latest release and add them under Settings, Capabilities, Skills.
Cursor, GitHub Copilot, Codex, and other agents that read Agent Skills
Copy the skill folders into your project:
git clone https://github.com/trustpin-cloud/ai-tools
mkdir -p .agents/skills
cp -r ai-tools/skills/trustpin-integration ai-tools/skills/trustpin-attestation ai-tools/skills/trustpin-cicd .agents/skills/.agents/skills/ is the shared project location these agents read. Agent-specific locations also work: .claude/skills/, .cursor/skills/, .github/skills/. Check your agent’s documentation if the skill is not picked up.
Agents without skills support
Keep the folders in your repository and add this line to AGENTS.md:
When working with TrustPin or certificate pinning, read
.agents/skills/trustpin-integration/SKILL.mdfirst; for app attestation, read.agents/skills/trustpin-attestation/SKILL.md.
Versions
The integration skill is verified against TrustPinKit 7.1.0, kotlin-sdk 7.1.0, trustpin_sdk 7.1.0, and @trustpin/react-native 7.1.0. The attestation skill is verified against TrustPinAttestKit, kotlin-attest, trustpin_attest and @trustpin/react-native-attest 7.1.0, and attest-verifier 1.0.0. The CI/CD skill targets trustpin-cli 7.0.0 and is written from TrustPin’s DevOps guide. The SDK API references are the most current source: Swift , Kotlin , Flutter , and React Native . If your installed SDK behaves differently, the SDK is the source of truth: tell your agent, or open an issue.
Feedback
Issues and corrections: github.com/trustpin-cloud/ai-tools/issues . Technical support: support@trustpin.cloud. Other inquiries: contact@trustpin.cloud. The skills are provided under the TrustPin Binary License Agreement (see the repository’s LICENSE).