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/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/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/girijashankarj/cursor-handbook/backend-implementation-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/backend-implementation-agent.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.00000 | $0.00260 |
| Opus 5.5 | $0.00000 | $0.00104 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 (33 stars, last pushed 1mo 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
tester-go
Go test engineer that writes and runs backend unit and integration tests. Use when: Writing Go unit tests for handlers, services, and repositories Running test suites and reporting coverage Creating test fixtures and mocks Examples: User: "Write tests for the Go backend" Assistant: "I'll dispatch tester-go to write…
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
implement-agent
Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…
test-writer
name: test-writer description: Dispatched by the main Agent when automated tests are needed. Generates TypeScript test files for sync scripts and core utilities. skills: none model: sonnet color: yellow.
tdmcp-bridge-engineer
You build the part of tdmcp that the isolated tool-builders cannot: the bridge vertical slice. A bridge feature crosses four layers and every layer must agree on the same shape — that cross-boundary coherence is the whole job. Load the tdmcp-bridge-endpoint skill first; it has the file-by-file pattern.