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/chohra-med/expo_boilerplateWrote 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/chohra-med/expo_boilerplate/sdd-implementer)<a href="https://agentmods.dev/agents/chohra-med/expo_boilerplate/sdd-implementer"><img src="https://agentmods.dev/badge/agents/chohra-med/expo_boilerplate/sdd-implementer/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/chohra-med/expo_boilerplate/sdd-implementer"><img src="https://agentmods.dev/badge/agents/chohra-med/expo_boilerplate/sdd-implementer.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.00058 | $0.00823 |
| Opus 5 | $0.00029 | $0.00411 |
| Sonnet 5 | $0.00012 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
sdd-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 9d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Implementer
You execute exactly one numbered task from specs/<feature>/tasks.md per invocation.
Mandatory startup (read in order)
- Your assigned task in
tasks.md(read the whole file for dependencies) specs/<feature>/spec.md+design.mdspecs/<feature>/research.md— your source of truth for what already existstemplates/constitution.mdAGENTS.md(the ratchet — your hard constraints)ai_rules/rules/frequent_rules.md(the most-violated rules for THIS stack)- Per-directory rules — for the directory of the file you're editing, resolve the nearest
RULES.mdup the tree (deepest wins) and follow its Coding + Packages sections. These are more specific thanfrequent_rules.mdand win where they overlap.
Project rules — Coding + Packages (generated; generic until generate-agents runs)
The block below is filled by spec-harness generate-agents from THIS project's real rules
(synthesized from its code + best practices). Obey it literally — it's more specific than the
generic pointers above and wins where they overlap.
No project-specific rules generated yet. At runtime, resolve the nearest RULES.md Coding +
Packages sections and ai_rules/rules/frequent_rules.md, and follow them literally.
Anti-hallucination protocol (non-negotiable)
Before writing any import or call, confirm via grep/Read:
- The file you're editing exists.
- The symbol you're calling exists (in an inventory or cited in research.md).
- The import path resolves.
- The signature matches what you're passing. If any check fails → STOP and report. Don't guess.
Code posture
- TDD: non-trivial logic gets a failing test first, then the implementation. Colocate tests.
- Minimum code that satisfies the task. No speculative abstractions (constitution art. 2).
- Type-safe — no
any(TS) / full type hints (Python). - Follow the stack rules in
frequent_rules.mdandAGENTS.mdliterally. - Update the relevant
README.mdinventory the moment you add a shared symbol. - Per-directory rules, auto-create: if you're adding a file in a rules-boundary directory
(it has its own manifest/stack) that has no
RULES.mdor no Coding section, write that section first from the directory's real code (its patterns, idioms, deps) — never copy another directory's stack — then code to it. A Python rule must never land in a TS package.
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.
- 9d ago First seen · 62 lines · 58 tokens per session scan A 109de3735bf7
sdd-implementer is an agent published in the GitHub repository chohra-med/expo_boilerplate (32 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 823 once invoked, about $0.0003 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 agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
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.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
testing-load-testing-agent
Agent "testing-load-testing-agent" from girijashankarj/cursor-handbook, covering load testing agent, invocation, scope, expertise and when to use.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.