Gentle-AI configures an existing AI coding agent into an engineering environment with persistent memory, planning workflows, skills, tool servers, model routing, and optional review. Developers and teams use it to make coding agents follow project conventions and retain decisions across sessions. The catalogue entries are its skills, commands, agents, and instruction.
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/gentleman-programming/gentle-ai/sdd-verifygit clone --depth 1 https://github.com/Gentleman-Programming/gentle-aiWrote 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-ai/sdd-verify)<a href="https://agentmods.dev/agents/gentleman-programming/gentle-ai/sdd-verify"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-ai/sdd-verify.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00605 |
| Opus 5 | $0.00018 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
sdd-verify 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 5d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SDD verify executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
Instructions
Read the skill file at ~/.claude/skills/sdd-verify/SKILL.md and follow it exactly.
Also read shared conventions at ~/.claude/skills/_shared/sdd-phase-common.md.
Execute all steps from the skill directly in this context window:
- Read spec artifact (required): read the
specartifact from the orchestrator-injected locator (seesdd-phase-common.mdsection B) - Read tasks artifact (required): read the
tasksartifact from the orchestrator-injected locator (seesdd-phase-common.mdsection B) - Read apply-progress (required): read the
apply-progressartifact from the orchestrator-injected locator (seesdd-phase-common.mdsection B) - Run the test suite appropriate to the stack (use terminal/MCP as needed)
- Check each spec requirement against implementation — flag CRITICAL / WARNING / SUGGESTION
- Confirm tasks are marked complete and match code state
- Persist verify report to active backend
Engram Save (mandatory)
After completing work, call mem_save with:
- title:
"sdd/{change-name}/verify-report" - topic_key:
"sdd/{change-name}/verify-report" - type:
"architecture" - project:
{project-name from context} - capture_prompt:
falsewhen the Engram tool schema supports it; if an older schema rejects or does not expose the field, omit it rather than failing.
Result Contract
Return a structured result with these fields:
status:done|blocked|partialexecutive_summary: one-sentence verdict (CRITICAL count, WARNING count, SUGGESTION count)artifacts: topic_keys or file paths written (e.g.sdd/{change-name}/verify-report)next_recommended:sdd-archive(if clean) orsdd-apply(if CRITICAL issues found)risks: unresolved CRITICAL issues that block archiveskill_resolution:paths-injectedif exact skill paths were provided and loaded, otherwisenone
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.
- 5d ago First seen · 46 lines · 0 tokens per session scan A f58f92a54dc6
sdd-verify is an agent published in the GitHub repository Gentleman-Programming/gentle-ai (6,194 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 605 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.