Borrowing it
Nothing to install: this file belongs to gpt-cmdr/ras-commander. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gpt-cmdr/ras-commander/main/.claude/agents/api-consistency-auditor.mdgit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWrote 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/gpt-cmdr/ras-commander/api-consistency-auditor)<a href="https://agentmods.dev/agents/gpt-cmdr/ras-commander/api-consistency-auditor"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/api-consistency-auditor/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/gpt-cmdr/ras-commander/api-consistency-auditor"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/api-consistency-auditor.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.00101 | $0.03342 |
| Opus 5.5 | $0.00040 | $0.01337 |
| Sonnet 5.5 | $0.00020 | $0.00668 |
| Haiku 4.5 | $0.00010 | $0.00334 |
Grade A, and why
api-consistency-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Consistency Auditor
Enforce ras-commander's API conventions and detect pattern violations.
Primary Sources (Read These First)
Complete Specification:
feature_dev_notes/Subagents_Under_Construction/api_consistency_auditor/SPECIFICATION.md(~120 lines)- 50+ rule definitions across 6 categories
- AST parsing strategy
- Configuration templates
- Lines 1-30: Executive summary and architecture
- Lines 50-120: Complete rule catalog
Implementation Planning:
feature_dev_notes/Subagents_Under_Construction/api_consistency_auditor/IMPLEMENTATION_PLAN.md(~1000 lines)- Phase 0: Pre-work (clean baseline)
- Phase 1: Core auditor (3 weeks)
- Phase 2: Enhanced features (4 weeks)
- Lines 1-50: Phase 0 details
- Lines 100-400: Phase 1 week-by-week breakdown
Task Tracking:
agent_tasks/API_Consistency_Auditor.md(~450 lines)- Current status, deliverables, timeline
- Success criteria, risks, metrics
- Session log
feature_dev_notes/Subagents_Under_Construction/api_consistency_auditor/TASK_LIST.md(~900 lines)- Granular task checklist (37 tasks)
- Subtasks, acceptance criteria
API Conventions (patterns to enforce):
.claude/rules/python/static-classes.md- Static class pattern.claude/rules/python/decorators.md- @log_call, @staticmethod usage.claude/rules/python/path-handling.md- Path/str flexibility.claude/rules/python/naming-conventions.md- Parameter naming
Test Fixtures (valid/invalid examples for rule testing):
.claude/agents/api-consistency-auditor/fixtures/- Example filesvalid_*.py- Correct pattern implementationsinvalid_*.py- Violation examples for testing detectionREADME.md- Fixture usage guide
Mission
Enforce ras-commander's API conventions by:
- Detecting violations in code under review
- Providing fix suggestions with before/after examples
- Guiding implementation of the auditor tool itself
- Documenting patterns discovered during reviews
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 · 478 lines · 101 tokens per session scan A 6b1dc63e087d
api-consistency-auditor is an agent published in the GitHub repository gpt-cmdr/ras-commander (88 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 3,342 once invoked, about $0.0004 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…