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 shrimbly/project-wiki --skill new-project-wikigit clone --depth 1 https://github.com/shrimbly/project-wikiWrote 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/shrimbly/project-wiki/new-project-wiki)<a href="https://agentmods.dev/skills/shrimbly/project-wiki/new-project-wiki"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/new-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/shrimbly/project-wiki/new-project-wiki"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/new-project-wiki.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.00117 | $0.01455 |
| Opus 5.5 | $0.00047 | $0.00582 |
| Sonnet 5.5 | $0.00023 | $0.00291 |
| Haiku 4.5 | $0.00012 | $0.00145 |
Grade A, and why
new-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 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-project-wiki
Why a project-wiki?
A project-wiki turns scattered, messy inputs — documents, meeting transcripts, web pages, design files, pasted notes — into a durable, cross-linked knowledge base that an agent builds and keeps current. Every source is captured faithfully, then synthesized into interlinked pages — the key entities, concepts, decisions, and open questions — that you can browse and comment on in a local viewer. Once it exists, you mostly just ask the agent questions and it stitches answers across the whole thing. It's a good fit for designing a system, researching a domain, capturing decisions and their rationale, or getting people up to speed on something complex.
What this skill does
Sets up a brand-new project-wiki in its own folder next to your current project, then runs an interactive setup: it names and configures the wiki, brands its viewer, and optionally pulls in any starting material you already have — so you end with a ready-to-use knowledge base.
Heads-up: this downloads a copy of the public
project-wikistarter repo into a new folder beside your current project and sets it up there. It only reads a public GitHub repo and works inside the new folder — it never changes or pushes your current project.
The starter repo it pulls from (point this at your own copy if you have one):
TEMPLATE_URL = https://github.com/shrimbly/project-wiki
1. Resolve where the new project goes
The new project is created as a sibling of the current project:
ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)" # current project root
PARENT="$(dirname "$ROOT")" # sibling location
2. Name the wiki (interactive)
Ask what the wiki is about — usually the project or topic it will document (e.g. "Billing System Redesign").
Encourage naming it <Project> Wiki — with "wiki" on the end. This folder is the
wiki for the project, not the project itself, so the name should keep the two
distinct (you don't want a billing-system-redesign wiki repo sitting next to the
actual billing-system-redesign project and getting confused for it). So:
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 · 123 lines · 117 tokens per session scan A 25304079c124
new-project-wiki is a skill published in the GitHub repository shrimbly/project-wiki (6 stars, last pushed 3mo ago), licensed MIT. It adds 117 tokens to every session and 1,455 once invoked, about $0.0005 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…