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 skills add evb87-tech/corpus --skill roadmap-updategit 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/skills/evb87-tech/corpus/roadmap-update)<a href="https://agentmods.dev/skills/evb87-tech/corpus/roadmap-update"><img src="https://agentmods.dev/badge/skills/evb87-tech/corpus/roadmap-update/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/skills/evb87-tech/corpus/roadmap-update"><img src="https://agentmods.dev/badge/skills/evb87-tech/corpus/roadmap-update.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.00094 | $0.01966 |
| Opus 5.5 | $0.00038 | $0.00786 |
| Sonnet 5.5 | $0.00019 | $0.00393 |
| Haiku 4.5 | $0.00009 | $0.00197 |
Grade A, and why
roadmap-update 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vous produisez un document de roadmap à destination de $CORPUS_VAULT/output/, commandé via /pm-roadmap-update. L'argument optionnel $ARGUMENTS fournit un titre ou un périmètre (ex. : « Q2 orienté clients »).
Règles fondamentales (anti-lissage)
Ces règles s'appliquent sans exception. Voir corpus-core/rules/07-anti-lissage.md.
- Ne jamais inventer une priorité. Si le wiki ne documente pas la priorité d'un epic, écrivez
[priorité non documentée dans le wiki]— n'en déduisez pas une depuis votre connaissance d'entraînement. - Ne jamais compléter silencieusement. Si le wiki est vide de décisions, dites-le explicitement. Ne produisez pas de section « Vision » avec du discours stratégique générique.
- Ne jamais harmoniser les contradictions. Si deux décisions wiki se contredisent sur le périmètre, citez les deux et signalez le conflit sous la section concernée.
- Citer toutes les pages wiki consultées à la fin du document, sous
## Sources. - La roadmap est un livrable
output/. Elle ne doit jamais être déposée danswiki/. Voircorpus-core/rules/01-folder-discipline.md.
Étape 1 — Vérifier la présence de bd
Avant toute chose, vérifiez que la commande bd est disponible dans le runtime :
which bd 2>/dev/null || echo "ABSENT"
Si bd est absent, refusez avec le message suivant et arrêtez :
Erreur :
bdest introuvable dans le runtime. La commande/pm-roadmap-updaterequiert l'outil beads (bd) pour lire les epics. Installez-le : https://github.com/draftcode/beads (ou suivez les instructions de votre équipe). Une fois installé, relancez/pm-roadmap-update.
Étape 2 — Lire les epics beads
Exécutez :
bd list --type epic --json --limit 0
Le flag --json est un flag global de bd ; --limit 0 désactive la pagination (50 par défaut).
Si la commande échoue (erreur de base de données, répertoire .beads absent, etc.), refusez avec un message explicite indiquant la commande qui a échoué et son message d'erreur. Ne continuez pas.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 199 lines · 94 tokens per session scan A ed3915d15a58
roadmap-update is a skill published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. It adds 94 tokens to every session and 1,966 once invoked, about $0.0004 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-31.
Other skills, from other repositories
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
superbrain-recall
Search the user's SuperBrain second-brain vault. Use whenever the user references past work, prior decisions, "how did we", "did we already", earlier sessions, a project's history, or anything that may already be recorded — before answering from scratch.
project-consolidation
Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.