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/ryo-ebata/cc-audit/safe-buildgit clone --depth 1 https://github.com/ryo-ebata/cc-auditWrote 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/ryo-ebata/cc-audit/safe-build)<a href="https://agentmods.dev/commands/ryo-ebata/cc-audit/safe-build"><img src="https://agentmods.dev/badge/commands/ryo-ebata/cc-audit/safe-build.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.00000 | $0.00087 |
| Opus 5 | $0.00000 | $0.00044 |
| Sonnet 5 | $0.00000 | $0.00017 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
safe-build 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.
What it actually says
Build Command
Build the application for development or production.
Usage
Run this command to build the project.
Steps
- Install dependencies
- Run type checking
- Build for production
# Install dependencies
npm install
# Type check
npm run typecheck
# Build
npm run build
Output
Build artifacts will be placed in the dist/ directory.
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 · 29 lines · 0 tokens per session scan A 523ebbc1c40f
safe-build is a command published in the GitHub repository ryo-ebata/cc-audit (24 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 87 tokens. 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
review
Comprehensive code review for blz changes.
format-sync
Mirror a data-format change across the Rust and Node implementations, prove conformance, and add a fixture.
ccboard-install
Install or update ccboard.
axon-deploy
Deploy or restart the axon stack (qdrant, tei, chrome, axon) via docker compose.
test-rust
Run Rust tests for Solana programs and backend services.
build-program
Build Solana program (Anchor or native).