Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ComeOnOliver/skillshub --skill axiom-code-signinggit clone --depth 1 https://github.com/ComeOnOliver/skillshubWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/comeonoliver/skillshub/axiom-code-signing)<a href="https://agentmods.dev/skills/comeonoliver/skillshub/axiom-code-signing"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-code-signing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/comeonoliver/skillshub/axiom-code-signing"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-code-signing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00061 | $0.04507 |
| Opus 5 | $0.00030 | $0.02253 |
| Sonnet 5 | $0.00012 | $0.00901 |
| Haiku 4.5 | $0.00006 | $0.00451 |
Grade A, and why
axiom-code-signing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Signing
Certificate management, provisioning profiles, entitlements configuration, CI/CD signing setup, and distribution build preparation for iOS/macOS apps.
When to Use This Skill
Use when you need to:
- ☑ Set up code signing for a new project or CI/CD pipeline
- ☑ Debug any code signing error (certificate, profile, entitlement, Keychain)
- ☑ Configure signing for App Store, TestFlight, or Ad Hoc distribution
- ☑ Manage certificates and profiles across a team
- ☑ Set up fastlane match for team-wide certificate management
- ☑ Understand automatic vs manual signing tradeoffs
- ☑ Add a new capability that requires entitlement changes
- ☑ Fix CI/CD signing failures (errSecInternalComponent, locked keychain)
Example Prompts
"How do I set up code signing for my app?" "My build fails with 'No signing certificate found'" "How do I set up fastlane match for my team?" "errSecInternalComponent in GitHub Actions" "ITMS-90035 when uploading to App Store" "How do I add push notification entitlements?" "Multiple certificates match — ambiguous identity" "Code signing works locally but fails in CI" "How do I sign for App Store distribution?" "My provisioning profile expired, what do I do?"
Red Flags
Signs you're making this harder than it needs to be:
- ❌ Sharing certificates via Slack/email — .p12 files in chat create security risks and version confusion. Use fastlane match or Xcode's automatic signing.
- ❌ Disabling code signing to "fix" a build — Code signing can't be disabled for device or distribution builds. The error will return.
- ❌ Committing .p12 or .mobileprovision to git — These are secrets. Use CI secrets management (GitHub Secrets, environment variables).
- ❌ Regenerating all certificates "to be safe" — Revokes existing certs, breaking every team member and CI pipeline.
- ❌ Using a personal certificate for team/CI builds — When that person leaves or their cert expires, everything breaks.
- ❌ Ignoring "profile doesn't include signing certificate" warnings — This always becomes a build failure. Fix it now.
- ❌ Setting
CODE_SIGN_IDENTITY = ""to suppress errors — Defers the problem to archive/export where it's harder to debug. - ❌ Manually managing profiles for automatic-signing projects — Pick one approach. Mixing causes conflicts.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 457 lines · 61 tokens per session scan A 9145b081ff00
axiom-code-signing is a skill published in the GitHub repository ComeOnOliver/skillshub (63 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 4,507 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
scaffold-cli
Scaffolds a TypeScript CLI and npm package with the house toolchain, dual tsdown outputs, CLI contracts, changesets, and publishing templates. Use when asked to "scaffold a CLI" or "start an npm package". For an existing package release use autoship; for existing API ergonomics use dx-audit.
field-service
Build ServiceNow Field Service Management — wmorder work orders, wmtask tasks, wmresource technicians with skills/territories, dispatch/auto-assignment, mobile status updates, and time entries.
mobile-development
Configure ServiceNow Mobile (Now Mobile/Agent) — syssgmobileapp screens, card builders, push notifications, offline sync rules, mobile actions for barcode/GPS, and offline-queue change processing.
fluent-ci-cd
This skill should be used when the user asks to "set up ci for fluent", "github actions for servicenow", "deploy fluent from a pipeline", "fluent pull request checks", "automate now-sdk", or reports "keys.ts out of date" — anything about running the ServiceNow SDK (now-sdk) headless in CI/CD.
swift-preflight
Audit a Swift / iOS / macOS repo for Xcode Cloud and TestFlight release blockers before upload - pbxproj drift, static build numbers, missing ciscripts, macOS App Store entitlements/Info.plist, headless-CI keychain tests, ad-hoc signing entitlement rejections, and flaky-UITest release gating. Reports PASS/WARN/FAIL…