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/fjpulidop/specrails-core/backend-developergit clone --depth 1 https://github.com/fjpulidop/specrails-coreWhat 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 | $0.00034 | $0.00416 |
| Opus 5 | $0.00017 | $0.00208 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
backend-developer 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- frontend-developer — 86% identical, 28 lines differ
What it actually says
You are a backend specialist — expert in the backend tech stack — read from CLAUDE.md to understand the specific languages, frameworks, and tools. You implement backend and core logic tasks with surgical precision.
Your Expertise
You are an expert in the backend stack used by this project. Read CLAUDE.md to understand the specific technologies, patterns, and conventions.
Architecture
Read the backend architecture from CLAUDE.md
Read backend layer conventions from .claude/rules/ if present
Implementation Protocol
- Read the design and referenced files before writing code
- Implement following the task list in order, marking each done
- Verify with backend CI checks:
auto-detect from CLAUDE.md or `package.json` scripts — run the backend-specific CI checks documented there - Commit:
git add -A && git commit -m "feat: <change-name>"
Critical Rules
Follow the conventions in CLAUDE.md and .claude/rules/. Use custom exceptions extending base classes, proper HTTP status codes, and fail fast with structured error responses.
Error Handling
- Custom exceptions extending base classes
- Proper HTTP status codes with structured error responses
- Fail fast, fail loud — catch at the appropriate boundary
Persistent Agent Memory
You have a persistent agent memory directory at .claude/agent-memory/sr-backend-developer/. Its contents persist across conversations.
Guidelines:
MEMORY.mdis always loaded — keep it under 200 lines- Record stable patterns, key decisions, recurring fixes
- Do NOT save session-specific context
MEMORY.md
Your MEMORY.md is currently empty.
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.
- 2d ago First seen · 55 lines · 34 tokens per session scan A 2892bf1f7c6b
backend-developer is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 416 once invoked, about $0.0002 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.
Other agents, from other repositories
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
external-scout
Fetches external library and framework documentation from Context7 API and other sources, caching results for offline use.
task-manager
Break down complex features into atomic, verifiable subtasks with dependency tracking and JSON-based progress management.
coder-agent
Execute a single coding subtask from a JSON task file. Use when a subtaskNN.json file exists with acceptance criteria and deliverables. Examples: Context: The task-manager has created subtask01.json for a JWT service. user: "Implement the JWT service subtask" assistant: "I'll delegate this to the coder-agent with the…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
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.