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.5 | $0.00023 | $0.00329 |
| Sonnet 5.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 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.
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.
- 1mo 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 (36 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 823 once invoked, about $0.0002 per session on Opus 5.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
pn-testing-specialist
Specialist: TDD, smoke tests, and CI. Runs tests, fixes failures, loops until green. Invoke directly for test work or let pn-build route to it.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
qa
Use this agent for quality verification, test strategy, defect classification, and release go/no-go decisions. Invoke after the developer delivers an increment. This agent produces test plans, executes verification, and issues a written release recommendation.
ci-fixer
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.
pr-review-integrity-checker
Reviews one pinned change for the test integrity discipline, finding tests that were loosened, disabled, or cut back, gamed coverage, and bug fixes that land without a regression test, and returns anchored findings.
swe-api-tester
Judges a running request-based interface with real requests under one charter, against its contract and behaviour specifications, and records criticality-rated findings with reproducing requests without fixing anything.