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 commands/rapiercraftstudios/forgedock/ci-auditgit clone --depth 1 https://github.com/RapierCraftStudios/ForgeDockWrote 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/commands/rapiercraftstudios/forgedock/ci-audit)<a href="https://agentmods.dev/commands/rapiercraftstudios/forgedock/ci-audit"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/ci-audit.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.00026 | $0.05934 |
| Opus 5 | $0.00013 | $0.02967 |
| Sonnet 5 | $0.00005 | $0.01187 |
| Haiku 4.5 | $0.00003 | $0.00593 |
Grade A, and why
ci-audit 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 480 lines · 26 tokens per session scan A 16ffc94e7b66
ci-audit is a command published in the GitHub repository RapierCraftStudios/ForgeDock (118 stars, last pushed 24d ago), licensed AGPL-3.0. It adds 26 tokens to every session and 5,934 once invoked, about $0.0001 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 commands, from other repositories
compass-recall
Run a one-shot semantic recall against the active project's memory/ entries: top hits with relevance scores, anchor drift annotations, and links.
compass-search
Search compass session-summary frontmatter (name, concept, type, drift, body) across all recorded sessions. Returns ranked hits with timestamps and drift glyphs.
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.
conventions-check
Check AGENTS.md, CLAUDE.md, and the projected agent artifacts (skills, subagents, commands) against the repo's conventions.
new-sdk-app
Create and setup a new Claude Agent SDK application.
modernize-harden
Security vulnerability scan with a reviewable remediation patch — OWASP, CWE, CVE, secrets, injection.