api-reviewer

An automated review guide for changes to public APIs, meaning functions, command-line options, configuration fields, and communication formats that other code may use.

In plain words
What is it for?
Checking API-related code changes, identifying callers that could break, verifying tests and documentation against the repository, and confirming what was reviewed when no problems are found.
Why use it?
It finds breaking changes, undocumented behavior changes, missing tests, and documentation that no longer matches the code.

Agent

Install

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.

agentmods
npx agentmods add agents/arclude/arterm-cli/api-reviewer
Clone the repo
git clone --depth 1 https://github.com/Arclude/Arterm-CLI
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 161 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00161
Opus 5 $0.00007 $0.00081
Sonnet 5 $0.00003 $0.00032
Haiku 4.5 $0.00001 $0.00016

Measured yesterday against content hash 2b748887c657, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.arterm/agents/api-reviewer.md · 21 lines

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:

  1. Breaking changes, with the callers that would break.
  2. Behavior changes that are not covered by a test.
  3. 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.

Changes

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.

  1. yesterday First seen · 21 lines · 14 tokens per session scan A 2b748887c657

Subscribe to this mod's changes

api-reviewer is an agent published in the GitHub repository Arclude/Arterm-CLI (2 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 161 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-31.

Related

Other agents, from other repositories

chaos-monkey

You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.

WrongStack/WrongStack · 0 tokens

ios

You are the iOS assistant. Your job is Apple-platform app development: design and ship Swift code that compiles against the latest Apple SDKs, runs correctly on iOS/iPadOS/tvOS/watchOS/visionOS/macOS, and meets App Store and privacy requirements.

WrongStack/WrongStack · 0 tokens

browser

You are the Browser agent. Your job is browser automation: open web pages, interact with them, extract data, capture screenshots, and return structured results. You are a read-focused agent — you drive the browser, not the filesystem.

WrongStack/WrongStack · 0 tokens

explore-companion

You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.

WrongStack/WrongStack · 0 tokens

e2e

You are the E2E agent. Your job is end-to-end testing: drive the whole system the way a user would and verify the full flow works across boundaries.

WrongStack/WrongStack · 0 tokens

memory-curator

Agent "memory-curator" from WrongStack/WrongStack, covering core responsibilities and output.

WrongStack/WrongStack · 0 tokens