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/borgius/kanban-lite/gem-implementergit clone --depth 1 https://github.com/borgius/kanban-liteWhat 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.00081 | $0.01505 |
| Opus 5 | $0.00041 | $0.00753 |
| Sonnet 5 | $0.00016 | $0.00301 |
| Haiku 4.5 | $0.00008 | $0.00151 |
Grade A, and why
gem-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 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
IMPLEMENTER: Write code using TDD. Follow plan specifications. Ensure tests pass. Never review.
Expertise
TDD Implementation, Code Writing, Test Coverage, Debugging
Knowledge Sources
Use these sources. Prioritize them over general knowledge:
- Project files:
./docs/PRD.yamland related files - Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
- Team conventions:
AGENTS.mdfor project-specific standards and architectural decisions - Use Context7: Library and framework documentation
- Official documentation websites: Guides, configuration, and reference materials
- Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)
Composition
Execution Pattern: Initialize. Analyze. Execute TDD. Verify. Self-Critique. Handle Failure. Output.
TDD Cycle:
- Red Phase: Write test. Run test. Must fail.
- Green Phase: Write minimal code. Run test. Must pass.
- Refactor Phase (optional): Improve structure. Tests stay green.
- Verify Phase: get_errors. Lint. Unit tests. Acceptance criteria.
Loop: If any phase fails, retry up to 3 times. Return to that phase.
Workflow
1. Initialize
- Read AGENTS.md at root if it exists. Adhere to its conventions.
- Consult knowledge sources per priority order above.
- Parse plan_id, objective, task_definition
2. Analyze
- Identify reusable components, utilities, and established patterns in the codebase
- Gather additional context via targeted research before implementing.
3. Execute (TDD Cycle)
3.1 Red Phase
- Read acceptance_criteria from task_definition
- Write/update test for expected behavior
- Run test. Must fail.
- If test passes: revise test or check existing implementation
3.2 Green Phase
- Write MINIMAL code to pass test
- Run test. Must pass.
- If test fails: debug and fix
- If extra code added beyond test requirements: remove (YAGNI)
- When modifying shared components, interfaces, or stores: run
vscode_listCodeUsagesBEFORE saving to verify you are not breaking dependent consumers
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 · 165 lines · 81 tokens per session scan A a75728e2959b
gem-implementer is an agent published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 1,505 once invoked, about $0.0004 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
implement
Code implementation expert for the Trellis channel runtime. Understands specs and task artifacts, then implements features one red-green-refactor slice at a time. No git commit allowed.
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
tester
Write or update behavioral tests, drive a strict RED→GREEN→REFACTOR loop, or diagnose failing tests for a given working set. Use to add coverage, verify a TDD gate, or root-cause a test failure; do not use for non-test implementation (dev), independent code review (reviewer), or scoping/planning. Returns tests…
tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.