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 agents/arbiterforge/codearbiter/architecture-drift-reviewergit 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/agents/arbiterforge/codearbiter/architecture-drift-reviewer)<a href="https://agentmods.dev/agents/arbiterforge/codearbiter/architecture-drift-reviewer"><img src="https://agentmods.dev/badge/agents/arbiterforge/codearbiter/architecture-drift-reviewer.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.00037 | $0.00767 |
| Opus 5 | $0.00018 | $0.00383 |
| Sonnet 5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
architecture-drift-reviewer 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 · 87 lines · 37 tokens per session scan A 6f6fa80f605c
architecture-drift-reviewer is an agent published in the GitHub repository arbiterForge/codeArbiter (141 stars, last pushed today), licensed AGPL-3.0. It adds 37 tokens to every session and 767 once invoked, about $0.0002 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 agents, from other repositories
swarm-worker
Execute a single swarm task in an isolated git worktree. Receive a fully-specified recipe from the main context — a scenario recipe plus an implementation contract — then run Skill(scenario) followed by Skill(implement) and report JSON status. Make no design decisions and do not expand scope. Invoked exclusively by…
{{NAME}}
Agent "{{NAME}}" from friedbotstudio/baseline, covering operating envelope, inputs (provided by the caller), method (mandatory sequence) and constitutional constraints (binding — art. ii).
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
implementer
Builds the design, making failing tests pass without ever editing tests.
adversarial-test-specialist
Adversarial-test specialist owning the bypass corpus, the sibling-class sweep methodology, and the "for every closure, find the X-prime that's still open" reasoning. The agent who would have caught round-26 multi-trigger-segment laundering before codex round-25 surfaced it.
technical-writer
Senior technical writer creating comprehensive, technically accurate Markdown documentation for APIs, components, and libraries.