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/azrtydxb/procoder/auditgit clone --depth 1 https://github.com/azrtydxb/procoderWhat 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.00027 | $0.00364 |
| Opus 5 | $0.00014 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
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 yesterday.
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
The user invoked /procoder:audit.
The command below is the procoder binary on PATH.
This is the onboarding sweep for a repository that was not built under procoder. Nothing is modified by the audit itself — you triage, plan, and fix with the user.
- Run
procoder doctor; if tools are missing, runprocoder initfirst — an audit full of NOT-checked lines wastes everyone's time. - Run
procoder index build, thenprocoder audit. Read the whole scorecard. - Triage in this order, and present the plan to the user BEFORE fixing:
- Secrets — every one needs removal AND rotation; check whether it
is a false positive first (a pinned SHA, a fixture) and use
gitleaks:allowor.gitleaksignorefor those, with a reason. - Other blocking — unformatted files (apply
procoder formatoutput), conflict markers, junk, template drift, failing terraform. - Judged info findings — lint, complexity, docs gaps: fix what is real in priority order, record reasons for what you leave.
- Secrets — every one needs removal AND rotation; check whether it
is a false positive first (a pinned SHA, a fixture) and use
- Fix incrementally — one theme per commit, gate-clean after each — and
re-run
procoder audituntil the scorecard says the repository would pass the gate. - Finish by writing the repo's
.procoder/files (procoder templatesprints defaults) so the standard holds from here on.
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.
- yesterday First seen · 30 lines · 27 tokens per session scan A 4d21ac092cb2
audit is a command published in the GitHub repository azrtydxb/procoder (196 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 364 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
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
test-report
Generate test execution report in markdown format.
add-test
Interactively add a new test definition to the test suite.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.