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 agentmods add skills/agent-sh/agnix/deploy-prodnpx skills add agent-sh/agnix --skill deploy-prodgit clone --depth 1 https://github.com/agent-sh/agnixWrote 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/agent-sh/agnix/deploy-prod)<a href="https://agentmods.dev/skills/agent-sh/agnix/deploy-prod"><img src="https://agentmods.dev/badge/skills/agent-sh/agnix/deploy-prod.svg" alt="Measured on agentmods" 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 | $0.00007 | $0.00027 |
| Opus 5 | $0.00003 | $0.00014 |
| Sonnet 5 | $0.00001 | $0.00005 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
deploy-prod 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 3d 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.
What it actually says
Deploy the application to production.
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.
- 3d ago First seen · 8 lines · 7 tokens per session scan A 287738dca204
deploy-prod is a skill published in the GitHub repository agent-sh/agnix (400 stars, last pushed 4d ago), licensed Apache-2.0. It adds 7 tokens to every session and 27 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
new-skill
Scaffold a new custom SKILL.md file interactively. Use when asked to create a new skill or slash command.
gh-issue
Create, view, list, or comment on GitHub issues. Use when asked to file, open, or manage GitHub issues.
gh-pr
Create, review, or manage GitHub pull requests. Use when asked to open, check, or merge a PR.
run-tests
Run the project test suite and surface failures. Use when asked to run tests or check test status.
branch
Create or switch to a feature branch, typically tied to a GitHub issue. Use when asked to create a branch or start work on an issue.
changelog
Generate a changelog or release notes from recent git history. Use when asked to write a changelog, summarize recent commits, or produce release notes.