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/evb87-tech/corpus/pm-strategist-examplegit clone --depth 1 https://github.com/evb87-tech/corpusWhat 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.00000 | $0.03423 |
| Opus 5 | $0.00000 | $0.01711 |
| Sonnet 5 | $0.00000 | $0.00685 |
| Haiku 4.5 | $0.00000 | $0.00342 |
Grade A, and why
pm-strategist-example 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 2d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exemple — /pm-review-strategy
Cet exemple illustre le comportement attendu du sous-agent
pm-strategistsur deux cas synthétiques. Il sert de référence pour les tests d'acceptance de cor-wx9.
Cas 1 — Brouillon contredisant wiki/decision-no-xml.md
Vault de départ (seeded)
wiki/
index.md
log.md
decision-no-xml.md — type: decision, décision: pas de support XML dans v1, alternatives écartées: XML, XLSX
feature-export-csv.md — type: feature, problème: export manuel laborieux
output/
2026-04-28-export-all-formats-prd.md
Contenu de wiki/decision-no-xml.md (extrait pertinent) :
---
type: decision
sources: [raw/architecture-review-2025.md]
last_updated: 2026-01-15
decision-date: 2026-01-15
---
# Pas de support XML en v1
## Résumé
L'équipe a décidé de ne pas implémenter l'export XML dans la version 1 du produit pour contenir la complexité initiale.
## Ce que disent les sources
- [[raw/architecture-review-2025.md]] : « Le support XML double le coût de maintenance du pipeline d'export sans bénéfice utilisateur démontré au stade v1. »
## Connexions
- [[wiki/feature-export-csv]] : fonctionnalité d'export retenue pour v1
## Contradictions
Aucune.
## Questions ouvertes
Réévaluation prévue pour v2 si la demande utilisateur le justifie.
## Date
2026-01-15
## Question
Faut-il inclure l'export XML dans le périmètre v1 ?
## Décision
Non. L'export XML est explicitement hors périmètre pour la v1. Seul le CSV est retenu.
## Alternatives écartées
- XML : coût de maintenance trop élevé sans bénéfice v1 démontré.
- XLSX : différé à v2 selon la demande.
## Personnes impliquées
Équipe architecture, PM.
## Sources
- [[raw/architecture-review-2025.md]]
Contenu du brouillon output/2026-04-28-export-all-formats-prd.md (extrait) :
---
type: prd
feature: export tous formats
date: 2026-04-28
status: draft
---
# PRD — Export tous formats
## Problème
Les utilisateurs ont besoin d'exporter leurs données dans plusieurs formats pour s'intégrer à leurs outils métier.
## Exigences
- [P0] L'utilisateur peut exporter en CSV.
- [P0] L'utilisateur peut exporter en XML pour les intégrations legacy.
- [P1] L'utilisateur peut exporter en XLSX.
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.
- 2d ago First seen · 333 lines · 0 tokens per session scan A 71a3f56ca0b3
pm-strategist-example is an agent published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,423 tokens. 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 agents, from other repositories
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
people-profiler
Bulk create or update person notes from Slack profiles. Given user IDs or names, checks Slack for role/title/team, checks vault for existing notes, creates missing ones, updates stale ones, and updates People & Context index.
slack-archaeologist
Deep reconstruction of Slack conversations. Given channel/DM/thread URLs, reads every message, every sub-thread, every profile, and produces a structured timeline with attribution. Use for incident reconstruction, evidence gathering, or any situation requiring full Slack context.
vault-librarian
Run vault maintenance: detect orphan notes, find broken wikilinks, validate frontmatter completeness, flag stale active notes, check cross-linking integrity. Invoke via /om-vault-audit or when the user asks for vault cleanup.
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…