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 skills/evb87-tech/corpus/feature-specnpx skills add evb87-tech/corpus --skill feature-specgit 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.00088 | $0.01578 |
| Opus 5 | $0.00044 | $0.00789 |
| Sonnet 5 | $0.00018 | $0.00316 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
feature-spec 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vous rédigez un PRD pour la fonctionnalité décrite dans $ARGUMENTS, à destination de $CORPUS_VAULT/output/.
Règles fondamentales (anti-lissage)
Ces règles s'appliquent sans exception. Voir corpus-core/rules/07-anti-lissage.md.
- Ne jamais inventer un persona. Si aucune page
persona-*n'existe dans le wiki, ne rédigez pas de section User Stories ou Personas sans l'avoir signalé. Marquez la section[lacune — aucun persona dans le wiki]et proposez au propriétaire de déposer une source dansraw/. - Ne jamais inventer un concurrent. Si aucune page
competitor-*n'existe, marquez la section Positionnement[lacune — aucun concurrent dans le wiki]. - Ne jamais compléter silencieusement avec des connaissances d'entraînement. Si une section requiert des informations absentes du wiki, signalez la lacune explicitement. Vous pouvez proposer un contenu de remplissage marqué
[non vérifié — connaissance d'entraînement, non tracée dans le wiki]uniquement si le propriétaire l'accepte explicitement. - Ne jamais harmoniser les contradictions. Si deux pages wiki se contredisent, citez les deux et placez le conflit dans une note sous la section concernée.
- Citer toutes les pages wiki consultées à la fin du document, sous
## Sources wiki.
Taxonomie des sections du PRD
Le PRD produit les sections suivantes, dans cet ordre, en français. Les titres de section sont fixes (ne pas traduire ni reformuler).
1. Problème
Décrivez le problème utilisateur ou métier que cette fonctionnalité résout. Basez-vous sur :
- les champs
## Frictionset## Motivationsdes pagespersona-* - les champs
## Problèmedes pagesfeature-*connexes
Si aucune page pertinente n'existe : [lacune — problème non documenté dans le wiki].
2. Objectifs
Listez les objectifs mesurables de la fonctionnalité. Reliez chaque objectif à une page wiki source quand c'est possible. Format recommandé : liste à puces.
3. Hors périmètre
Listez explicitement ce que cette fonctionnalité ne couvre PAS. Appuyez-vous sur :
- les décisions passées dans
decision-*(alternatives écartées) - les fonctionnalités connexes dans
feature-*qui couvrent déjà certains aspects
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.
- 2d ago First seen · 146 lines · 0 tokens per session scan A ef9a06e3b949
feature-spec is a skill published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It adds 88 tokens to every session and 1,578 once invoked, about $0.0004 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-31.
Other skills, from other repositories
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…