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-archive)<a href="https://agentmods.dev/agents/gentleman-programming/gentle-pi/sdd-archive"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-pi/sdd-archive/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-archive"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-pi/sdd-archive.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.02477 |
| Opus 5.5 | $0.00007 | $0.00991 |
| Sonnet 5.5 | $0.00003 | $0.00495 |
| Haiku 4.5 | $0.00002 | $0.00248 |
Grade A, and why
sdd-archive 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SDD archive 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.
Memory Contract
Read your own input artifacts directly from the active backend before doing the phase work; do not wait for the parent to inline them. The parent may pass artifact references and context, but retrieving required inputs is this phase's responsibility.
Inputs to read (engram/both: use the injected Engram memory read tools for the topic key, then fetch the full observation; openspec: read the files under openspec/changes/{change}/):
- All change artifacts:
sdd/{change}/proposal,sdd/{change}/spec,sdd/{change}/design,sdd/{change}/tasks,sdd/{change}/apply-progress,sdd/{change}/verify-report, andsdd/{change}/sync-reportif present.
Persist this phase's artifact to the active backend before returning (mandatory):
engram/both: call the injected Engram save tool with title andtopic_key"sdd/{change}/archive-report",type: "architecture",projectfrom context, andcapture_prompt: falsewhen the tool schema supports it (omit the field if an older schema rejects it).openspec: write the archive report and perform the file moves described in the sections below.none: return the archive report inline.
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 · +2 lines 94fc1b3f873f
- 1mo ago First seen · 208 lines · 17 tokens per session scan A 2db22fd8940f
sdd-archive 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 2,477 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
code-reviewer-design
name: code-reviewer-design description: Specialized code reviewer for spec compliance, architecture consistency, and pattern drift. Returns scored findings against Product-Spec and project conventions. skills: code-review model: inherit.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
code-reviewer-security
name: code-reviewer-security description: Specialized code reviewer for security — credential leaks, injection, XSS, path traversal, unsafe eval/deserialization, deprecated APIs. Returns scored findings. skills: code-review model: inherit.
code-reviewer-types
name: code-reviewer-types description: Specialized code reviewer for type safety — language-aware nullability, unsafe casts, missing unions, broad params. Returns scored findings. skills: code-review model: inherit.
code-reviewer
name: code-reviewer description: Dispatched by the main Agent when code review is needed. Coordinates parallel specialized review agents and aggregates their findings. skills: code-review model: opus color: red.
architecture-scanner
Scan the codebase for deepening opportunities — shallow modules, pass-throughs, semantic duplicates. Read-only. Produces a visual HTML report with before/after diagrams. Routes: CODEBASE-HEALTH workflow.