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.
git clone --depth 1 https://github.com/arbiterForge/codeArbiterWrote 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/arbiterforge/codearbiter/release)<a href="https://agentmods.dev/commands/arbiterforge/codearbiter/release"><img src="https://agentmods.dev/badge/commands/arbiterforge/codearbiter/release/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/commands/arbiterforge/codearbiter/release"><img src="https://agentmods.dev/badge/commands/arbiterforge/codearbiter/release.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.00000 | $0.00007 |
| Opus 5.5 | $0.00000 | $0.00003 |
| Sonnet 5.5 | $0.00000 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
release 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 1mo 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.
- 1mo ago Changed · -58 lines · -68 tokens per session 38ea3697585f
- 1mo ago Changed · +2 lines dd93d79cf672
- 1mo ago Changed a098e6361aab
- 1mo ago Changed · +1 lines · +13 tokens per session 0a3c4572c358
- 1mo ago First seen · 57 lines · 55 tokens per session scan A a6c5f8f98fd7
release is a command published in the GitHub repository arbiterForge/codeArbiter (149 stars, last pushed today), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 7 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
update-infos-release
Update Claude Code releases tracking (guide + landing + version bump).
release
Release guide version (CHANGELOG + VERSION + README + landing sync + commit + push).
finish-branch-execute
Step 4 of finishing-a-development-branch: Execute chosen integration option (merge, PR, PR+dance, keep, or discard).
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
doc-changelog
Generation and maintenance of the project changelog.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…