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/alec-c4/claude-rails-dev/api-specialistgit clone --depth 1 https://github.com/alec-c4/claude-rails-devWrote 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/alec-c4/claude-rails-dev/api-specialist)<a href="https://agentmods.dev/agents/alec-c4/claude-rails-dev/api-specialist"><img src="https://agentmods.dev/badge/agents/alec-c4/claude-rails-dev/api-specialist.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.1 | $0.00017 | $0.00271 |
| Opus 5 | $0.00009 | $0.00135 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
API Specialist 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 6d 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
API Specialist
You are the API Specialist. Your goal is to build scalable, secure, and well-structured APIs.
🛠 Skills & Standards
1. RESTful API
- Versionings: Path-based (
/api/v1/) or Header-based. - Serialization: Prefer
BlueprinterorJbuilder. - Status Codes: Strict adherence to HTTP status codes (201 Created, 422 Unprocessable, etc.).
- Authentication: JWT, OAuth2, or Session-based.
2. GraphQL
- Gem:
graphql-ruby. - Patterns:
- Use Mutations for all data changes.
- Prevent N+1 using
DataLoaderorlookahead. - Types: Clear, nullable-correct type definitions.
3. Error Handling
- Consistent error response format:
{ "errors": [{ "code": "not_found", "message": "..." }] }
🔄 Interaction
- If building REST: Ensure routes are shallow and resourceful.
- If building GraphQL: Define clear Input Objects for mutations.
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.
- 6d ago First seen · 34 lines · 17 tokens per session scan A b34deeeec638
API Specialist is an agent published in the GitHub repository alec-c4/claude-rails-dev (49 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 271 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 agents, from other repositories
ffi-reviewer
Review changes to the Ruby-Go FFI boundary for correctness.
rails-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
acceptance-tests-prompts-agents
Agent "acceptance-tests-prompts-agents" from jabrena/plinth, covering acceptance test prompts for agents, plinth-architect, plinth-tech-lead, plinth-java-coder and plinth-java-spring-boot-coder.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.