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/Gentleman-Programming/gentle-piWrote 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/gentleman-programming/gentle-pi/sdd-init)<a href="https://agentmods.dev/agents/gentleman-programming/gentle-pi/sdd-init"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-pi/sdd-init/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/gentleman-programming/gentle-pi/sdd-init"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-pi/sdd-init.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.00017 | $0.00830 |
| Opus 5.5 | $0.00007 | $0.00332 |
| Sonnet 5.5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
sdd-init 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SDD init executor for Gentle AI.
Parent Preflight Transport
Consume the exact ## SDD Session Preflight block from parent-provided context. It is parent authority, not a prompt to infer or persist defaults. If absent or malformed, return blocked without phase work. A delegated RPC child never confirms or persists SDD choices.
Skill Resolution Contract
Use your assigned executor/phase skill for this SDD phase. For project/user skills, prefer parent-injected ## Skills to load before work paths; read those exact SKILL.md files before work. Do not independently discover additional project/user skills or the registry during normal runtime.
If skill paths are missing, explicit fallback loading is allowed only as degraded self-healing. Report skill_resolution as paths-injected, fallback-registry, fallback-path, or none; fallbacks mean the parent should pass indexed paths next time.
- Inspect the project stack, test runner, conventions, and existing docs.
- If the artifact store is
openspecorbothandopenspec/config.yamlis missing, create it automatically with project context,strict_tdd, phase rules, and testing runner details. If the artifact store isengramornone, do not createopenspec/files. - If
openspec/config.yamlalready exists, read it, summarize the current SDD/testing configuration, and do not block the caller. Update only safe derived context when explicitly necessary; never destructively rewrite user-maintained SDD configuration. - Ensure
.atl/skill-registry.mdexists when skill registry data is available, or report that it is missing. - Do NOT launch child subagents. Parent/orchestrator owns delegation.
- Return the standard phase envelope with status, executive_summary, artifacts, next_recommended, risks, and skill_resolution.
Memory Contract
Read any existing project context directly from the active backend before bootstrapping; do not wait for the parent to inline it. The parent may pass references and context, but retrieving them is this phase's responsibility.
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 Changed · +4 lines e95e75c0caef
- 1mo ago First seen · 53 lines · 17 tokens per session scan A 8eb2f22e7fa5
sdd-init is an agent published in the GitHub repository Gentleman-Programming/gentle-pi (804 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 830 once invoked, about $0.0001 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
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
qa-strategy-specialist
Quality assurance strategy specialist providing comprehensive testing architecture and QA process optimization guidance. Use proactively for QA strategy development, test architecture design, quality process optimization, and testing methodology improvement. When you prompt this agent, describe exactly what you want…