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 StanfordSpezi/SpeziVibe --skill project-wikigit clone --depth 1 https://github.com/StanfordSpezi/SpeziVibeWrote 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/stanfordspezi/spezivibe/project-wiki)<a href="https://agentmods.dev/skills/stanfordspezi/spezivibe/project-wiki"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/project-wiki/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/stanfordspezi/spezivibe/project-wiki"><img src="https://agentmods.dev/badge/skills/stanfordspezi/spezivibe/project-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.02946 |
| Opus 5 | $0.00021 | $0.01473 |
| Sonnet 5 | $0.00008 | $0.00589 |
| Haiku 4.5 | $0.00004 | $0.00295 |
Grade A, and why
project-wiki 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 10d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Wiki
Set up and maintain a persistent knowledge base for a digital health project. Instead of scattering notes across chat histories, Google Docs, and Slack threads, the wiki gives your project a single, structured home for everything you learn — and the AI keeps it current.
Inspired by Andrej Karpathy's LLM Wiki pattern, adapted for the Stanford Biodesign innovation process.
When to Use
Use this skill when you want to:
- accumulate project knowledge that compounds over time instead of scattering across tools
- keep clinical observations, user interviews, literature, and competitive intelligence organized and cross-referenced
- maintain a living evidence base that updates as new information arrives
- give new team members a structured way to get up to speed on a project
Do not use this skill for one-off questions or quick research. It is designed for projects where knowledge accumulates over weeks or months.
The Core Idea
Most teams use AI the way they use search — ask a question, get an answer, move on. The AI rediscovers context from scratch every time. Nothing compounds.
A project wiki is different. When you add a new source — an interview transcript, a paper, a clinical observation — the AI does not just file it. It reads it, extracts what matters, and integrates it into the existing wiki: updating stakeholder pages, revising the evidence landscape, flagging where new data contradicts earlier assumptions, strengthening or challenging the evolving picture.
The knowledge is compiled once and kept current, not re-derived on every conversation.
You curate sources, direct the analysis, and ask the right questions. The AI does the summarizing, cross-referencing, filing, and bookkeeping.
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.
- 10d ago First seen · 299 lines · 42 tokens per session scan A 94eb7a1cf61a
project-wiki is a skill published in the GitHub repository StanfordSpezi/SpeziVibe (23 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 2,946 once invoked, about $0.0002 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 skills, from other repositories
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.
report
Writes the session final report to a file, then prints only the path and a one-line summary. Fires when the prompt contains "Report per memstack:report", and also when the prompt begins with a standing trigger configured through MEMSTACKREPORTONTASKPROMPTS or MEMSTACKREPORTTRIGGERS. Dormant otherwise.
token-optimization
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for…
compress
Use when the user says 'tokenstack', 'compression', 'token savings', 'proxy status', or asks about context window usage.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.