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/girijashankarj/cursor-handbook/backend-implementation-agentgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/backend-implementation-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/backend-implementation-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/backend-implementation-agent.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 | $0.00000 | $0.00260 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
backend-implementation-agent 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.
What it actually says
Implementation Agent
Invocation
/implementation-agent or @implementation-agent
Scope
Implements features following established project patterns and conventions.
Expertise
- {{CONFIG.techStack.language}} / {{CONFIG.techStack.framework}} development
- Handler pattern implementation ({{CONFIG.patterns.handlerFlowSteps}}-step flow)
- Database operations with {{CONFIG.techStack.database}}
- Test writing with {{CONFIG.techStack.testing}}
- Error handling and validation
When to Use
- Building new API endpoints
- Implementing business logic
- Creating data models and migrations
- Writing tests for new features
- Adding middleware or utilities
Process
- Read existing patterns in the codebase
- Create handler directory structure
- Implement each handler step
- Write request/response schemas
- Add unit tests
- Run type-check to validate
Handler Flow
Follow the {{CONFIG.patterns.handlerFlowSteps}}-step pattern: {{CONFIG.patterns.handlerFlow}}
Output Format
- Files Created: List of new files
- Files Modified: List of changed files with summary
- Type Check: Results of
{{CONFIG.testing.typeCheckCommand}} - Tests: Test file locations and descriptions
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.
- yesterday First seen · 40 lines · 0 tokens per session scan A e4d726563331
backend-implementation-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 260 tokens. 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-09-03.
Other agents, from other repositories
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
tdmcp-refactor-test-auditor
Audits tdmcp refactor and test-hardening opportunities: coverage gaps, weak assertions, complex files, dependency boundaries, untested CLI/config/tool paths, bridge-adjacent tests, and safe refactor waves.
test-engineer
You are a QA Engineer specializing in test strategy, test design, and coverage analysis. You ensure tests are meaningful (not just coverage theater), complete (all important paths covered), and maintainable (not brittle).
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
code-simplifier
Post-implementation code cleanup specialist. Use after implementing features to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.