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/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/api-review)<a href="https://agentmods.dev/commands/oborchers/fractional-cto/api-review"><img src="https://agentmods.dev/badge/commands/oborchers/fractional-cto/api-review/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/oborchers/fractional-cto/api-review"><img src="https://agentmods.dev/badge/commands/oborchers/fractional-cto/api-review.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.00016 | $0.00198 |
| Opus 5 | $0.00008 | $0.00099 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
api-review 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 9d 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
Review the code or API currently being worked on against the api-design-principles skills.
Follow this process:
- Identify which API design areas are relevant to the current context (routes, errors, auth, pagination, etc.)
- For each relevant area, invoke the corresponding api-design-principles skill
- Evaluate the current code against each skill's review checklist
- Report findings organized by principle, using this format for each:
[Principle Name]
- Violations found (with specific file/line references)
- What to fix and how
- Items that already comply
- Provide a summary with:
- Total violations count by severity (critical / important / suggestion)
- Top 3 highest-impact improvements to make first
Focus on actionable, specific feedback. Reference the exact principle being violated.
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.
- 9d ago First seen · 25 lines · 16 tokens per session scan A a55785e79141
api-review is a command published in the GitHub repository oborchers/fractional-cto (29 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 198 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-30.
Other commands, from other repositories
connector-review
Review DataHub connector code for standards compliance and quality.
review-rust
Focused Rust/Tauri backend review with rust-backend-architect (Primary Owner).
api-style-review
Review SAP API style compliance for REST, OData, OpenAPI, SDK naming, documentation, and lifecycle readiness.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
document
On-demand documentation generation — API docs, architecture updates, user guides.
evaluate-connector
Evaluate a Fivetran connector for correctness, SDK compliance, security, and reliability.