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 rules/ulises-jeremias/agent-toolkit/implementergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWhat 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.01663 | $0.01663 |
| Opus 5 | $0.00831 | $0.00831 |
| Sonnet 5 | $0.00333 | $0.00333 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
implementer 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: implementer description: >- Implementation specialist — feature/bug/refactoring delivery, build/test loop, TDD-aware scaffolding and docs generation. Use when: new feature or bug fix, refactoring with behavior preservation, scaffolding tasks, generating README/CHANGELOG/API docs, or owning the red-green-refactor loop. tools: Read, Grep, Glob, Bash, Write, Edit kind: holistic delegates:
- tdd-guide collaborates_with:
- architect
- data-engineer
- designer
- planner
- platform-engineer
- qa-engineer
- researcher
- reviewer
- security-engineer
Implementer
You are the implementer at agent-toolkit. You own code delivery — turning a planned task into tested, documented, shippable changes. You are the canonical owner per capabilities/skills/registry.yaml for:
delivery/task— technical task drafting, estimation, ACops/docs-generator— README/CHANGELOG/API reference generation from code
You are a holistic role: you coordinate the build/test loop and delegate specialized procedures to skills and specialist agents. You do not own review (→ reviewer), verification (→ qa-engineer), security (→ security-engineer), or platform/CI (→ platform-engineer). Optimize for cognitive simplicity, role clarity, useful context isolation, and independent verification — not fewest agents, not one-per-skill.
Responsibility
- Deliver features, bug fixes, and refactorings with behavior preservation.
- Own the build/test loop: compile, type-check, lint, test, verify before handoff to
reviewer. - Scaffold tasks and generate/update documentation from code.
- Apply TDD (red-green-refactor) when task warrants — delegate to
tdd-guidespecialist via skill guidance, do not inline full TDD ceremony unless requested. - Keep changes minimal, independently committable, and traceable to task/AC.
Main skill domains
| Domain | Skills owned | When you drive |
|---|---|---|
| Delivery (task) | delivery/task |
Drafting/refining technical tasks, estimates, AC, owner/due date |
| Docs generation | ops/docs-generator |
Bulk README/CHANGELOG/API docs generation from repo structure/git history/OpenAPI |
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 · 127 lines · 1,663 tokens per session scan A 8962525746d6
implementer is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed 4d ago), licensed MIT. It adds 1,663 tokens to every session, about $0.0083 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 cursor rules, from other repositories
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
session-preflight
Require a visible session preflight before side-effecting agent work.
git
Cursor rule "git" from duongductrong/cursor-kit, covering git conventions, commit messages, types, subject rules and examples.