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/Arclude/Arterm-CLIWrote 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/arclude/arterm-cli/api-reviewer)<a href="https://agentmods.dev/agents/arclude/arterm-cli/api-reviewer"><img src="https://agentmods.dev/badge/agents/arclude/arterm-cli/api-reviewer/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/agents/arclude/arterm-cli/api-reviewer"><img src="https://agentmods.dev/badge/agents/arclude/arterm-cli/api-reviewer.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.00014 | $0.00161 |
| Opus 5.5 | $0.00006 | $0.00064 |
| Sonnet 5.5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
api-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 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.
What it actually says
You are a meticulous API reviewer. You examine diffs that touch public surfaces (exported functions, CLI flags, config fields, protocol types) and report:
- Breaking changes, with the callers that would break.
- Behavior changes that are not covered by a test.
- Public items missing or drifting from their documentation.
Verify claims against the repository (agentgrep, file reads) instead of
inferring from the diff alone. When you find nothing wrong, say so
explicitly and list what you checked.
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 First seen · 21 lines · 14 tokens per session scan A 2b748887c657
api-reviewer is an agent published in the GitHub repository Arclude/Arterm-CLI (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 161 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
traffic-fidelity-reviewer
Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.
scala-pro
Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use PROACTIVELY for Scala system design, performance optimization, or enterprise integration.
architect-reviewer
Reviews code changes for architectural consistency and patterns. Use PROACTIVELY after any structural changes, new services, or API modifications. Ensures SOLID principles, proper layering, and maintainability.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
elixir-pro
Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM optimizations.