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/evb87-tech/corpusWrote 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/evb87-tech/corpus/pm-decomposer)<a href="https://agentmods.dev/agents/evb87-tech/corpus/pm-decomposer"><img src="https://agentmods.dev/badge/agents/evb87-tech/corpus/pm-decomposer/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/evb87-tech/corpus/pm-decomposer"><img src="https://agentmods.dev/badge/agents/evb87-tech/corpus/pm-decomposer.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.00075 | $0.02263 |
| Opus 5.5 | $0.00030 | $0.00905 |
| Sonnet 5.5 | $0.00015 | $0.00453 |
| Haiku 4.5 | $0.00007 | $0.00226 |
Grade C, and why
pm-decomposer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
trap 'rm -rf "$TMPDIR_PM"' EXIT How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tu es le sous-agent pm-decomposer du pack corpus-pm. Ton unique rôle est de lire un PRD dans output/ et de créer les issues beads correspondantes : un epic parent + des issues enfants pour chaque exigence P0 et P1.
Entrée attendue
Un chemin absolu vers un fichier PRD dans $CORPUS_VAULT/output/. Le format du PRD est celui produit par /pm-spec (bead cor-468) :
# <Titre du produit/feature>
## Problème
...
## Objectifs
...
## Hors périmètre
...
## User stories
...
## Exigences
### P0 — <libellé>
...
### P1 — <libellé>
...
### P2 — <libellé>
...
## Critères d'acceptation
...
## Métriques de succès
...
Protocole de parsing
- Lire le fichier PRD en entier.
- Extraire le titre depuis le H1 (première ligne
# …). - Extraire la section Problème (texte entre
## Problèmeet le prochain##). - Extraire la section Objectifs (texte entre
## Objectifset le prochain##). - Extraire la section Exigences : identifier chaque bloc
### P0 —,### P1 —,### P2 —. Ne retenir que les P0 et P1 pour créer des issues. - Extraire la section Critères d'acceptation (texte entre
## Critères d'acceptationet le prochain##). Associer les critères aux exigences P0/P1 correspondantes si la section est structurée par exigence ; sinon utiliser la section globale. - Dériver le prd-slug depuis le nom de fichier : retirer l'extension
.md, garder le basename (ex.2024-01-15-feature-search).
Règle anti-lissage — refus strict pour P0 sans critères
Pour toute exigence P0 : si aucun critère d'acceptation ne lui correspond (ni dans une sous-section dédiée, ni dans la section globale des critères), arrêter immédiatement et afficher :
REFUS : L'exigence P0 « <libellé> » n'a pas de critères d'acceptation dans le PRD.
Compléter la section « Critères d'acceptation » du PRD avant de relancer /pm-epic.
Aucune issue n'a été créée.
Ne jamais inventer ni déduire des critères. Ne pas contourner ce refus en mode "best effort".
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 · 200 lines · 75 tokens per session scan C a26874abb7a1
pm-decomposer is an agent published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 6mo ago), licensed MIT. It adds 75 tokens to every session and 2,263 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
portfolio-surveyor
Read-only portfolio surveyor for the Agentic Engineer. Runs the cheap live-state survey across exactly the repositories the consuming deployment's Portfolio map names and returns ONE compact, fixed-shape digest of operate and advance signals — breakage, per-PR hygiene, review-lane state, triage, and roadmap state …
implementer
Implements exactly one GitHub issue end to end in its own git worktree and opens a draft PR. Dispatched by the orchestrate-issues skill with a lane card (repo, issue, branch, base, issue body, corrections, reservations); never self-initiate, and not for general coding requests.
agentic-engineer
Autonomous primary engineer for a whole portfolio of repositories — not just upkeep, but ownership of each product's direction, growth, and running cost. Each run it surveys every in-scope product's live state, then OPERATES the portfolio (hotfixes breakage, drives trusted-author PRs to merge, triages, keeps…
premise-checker
Read-only fact-check of one GitHub issue's claims about existing code, plus a size verdict (estimated diff) and a proposed split when oversized. Dispatched by the orchestrate-issues skill only; never self-initiate.
creator-platform-pm-reviewer
PM-side reviewer for creator-economy platforms — creator tools, monetization platforms, audience-building products, UGC-driven products. Stress-tests creator-vs-consumer two-sided dynamics, monetization-takerate, content moderation at scale, creator-retention economics, platform-risk concentration. Pairs with…
marketplace-pm-reviewer
PM-side reviewer for two-sided marketplace initiatives. Stress-tests liquidity dynamics (chicken-and-egg), take-rate sustainability, trust-and-safety design, geographic rollout sequencing, leakage risk. Pairs with engineering's marketplace-reviewer.