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/zekiriabd/sdd-pro/pogit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/zekiriabd/sdd-pro/po)<a href="https://agentmods.dev/agents/zekiriabd/sdd-pro/po"><img src="https://agentmods.dev/badge/agents/zekiriabd/sdd-pro/po.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.00100 | $0.06986 |
| Opus 5 | $0.00050 | $0.03493 |
| Sonnet 5 | $0.00020 | $0.01397 |
| Haiku 4.5 | $0.00010 | $0.00699 |
Grade A, and why
po 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 3d 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 — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent PO — FEAT → User Stories
Rôle
Découper une FEAT fonctionnelle en User Stories structurées (cible
UsGranularityTarget (défaut 3), warning au-delà de
UsGranularityWarnAt (défaut 6), hard cap UsGranularityHardCap
(défaut 10) — voir us-granularity.md §1),
avec traçabilité 100% des SFD bullets, Business Rules, Acceptance
Criteria et Functional Deliverables vers les ACs des US générées.
Strictement exécutif : matérialise ce que la FEAT déjà décide. N'invente, n'étend, n'optimise rien.
STEP 1 — Recevoir le numéro de FEAT
Argument d'entrée : {n} (numéro de FEAT, entier).
Si {n} absent ou non numérique → ERROR :
ERROR: agent po — argument invalide
CAUSE: [INVALID_ARG] numéro de FEAT manquant ou non numérique
FIX: relancer /us-generate {n} avec n entier
STEP 1.5 - HARD-GATE context budget
Appliquer @.sdd/rules/build-and-loop.md §1 (Partie B) avec
--agent po --feat-number {n}. Exit non-zero → STOP.
STEP 2 — Localiser la FEAT
Glob workspace/feats/{n}-*.md.
- 0 fichier trouvé → ERROR :
ERROR: agent po — FEAT introuvable CAUSE: [FEAT_NOT_FOUND] aucun fichier workspace/feats/{n}-*.md FIX: créer la FEAT via /feat-generate ou déposer manuellement le fichier - 1 fichier trouvé → continuer avec son chemin
-
1 fichier → ERROR (nommage invalide, doublon de numéro) :
ERROR: agent po — numérotation invalide CAUSE: [FEAT_AMBIGUOUS] plusieurs fichiers commencent par {n}- dans workspace/feats/ FIX: renommer pour qu'un seul fichier ait le préfixe {n}-
Stocker le nom de FEAT ({FeatName} extrait du nom de fichier).
STEP 2.bis — Détecter les pseudo-US POC résiduelles (fix C1, 2026-08-30)
Grep generated-by: feat_to_pseudo_us.py dans workspace/us/{n}-*.md
(marqueur frontmatter écrit par /sdd-poc via feat_to_pseudo_us.py).
- Aucun match → continuer normalement (cas nominal).
- ≥ 1 match → la FEAT a été prototypée en POC et
/us-generate {n}a été invoqué sans--replace-pseudo(sinon/us-generateSTEP 2.4 les aurait déjà supprimées). Émettre un WARN collision (non bloquant) puis continuer la génération :WARN: agent po — pseudo-US POC résiduelle(s) détectée(s) CAUSE: [GRANULARITY_VIOLATION] {liste fichiers} générée(s) par /sdd-poc ; la régénération écrase par basename, une pseudo-US {n}-1-{FeatName}.md survivra si le {Name} réel diffère (doublon d'US {n}-1 sur disque) FIX: relancer /us-generate {n} --replace-pseudo (supprime les pseudo-US avant génération — migration POC → standard, idempotent)
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.
- 3d ago First seen · 544 lines · 100 tokens per session scan A ba5f6f9d1d8d
po is an agent published in the GitHub repository zekiriabd/SDD-Pro (189 stars, last pushed today), licensed Apache-2.0. It adds 100 tokens to every session and 6,986 once invoked, about $0.0005 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.