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 wiki-querygit 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/wiki-query)<a href="https://agentmods.dev/skills/shrimbly/project-wiki/wiki-query"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/wiki-query/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/wiki-query"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/wiki-query.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.00085 | $0.00520 |
| Opus 5.5 | $0.00034 | $0.00208 |
| Sonnet 5.5 | $0.00017 | $0.00104 |
| Haiku 4.5 | $0.00009 | $0.00052 |
Grade A, and why
wiki-query 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.
What it actually says
wiki-query
Answer from the wiki — and capture the answer if it's worth keeping.
1. Find the relevant pages
- Read
wiki/index.mdfirst to locate the pages the question touches, then drill into them. Follow cross-links. - Check
wiki/open-questions.md— the question may already be tracked as open.
2. Answer
- If the wiki holds the answer, give it and cite the page(s) (by name and
viewer URL, e.g.
/wiki-concepts-foo/). - If the wiki is silent or thin, fall back to the
sources/captures and synthesize — but say that you're reasoning from sources, and flag uncertainty. - If the answer genuinely isn't in the material, say so plainly rather than
inventing it. Offer to
/wiki-researchit.
3. File non-trivial answers back
If the answer is more than a lookup — a comparison, a connection across pages, an analysis, a resolved ambiguity — it's wiki-worthy:
- Add a new
wiki/concepts/<name>.md(or the right type), or update an existing page, with the synthesis. Cite the pages/sources it draws on. - If the question exposed a real gap or contradiction, add it to
wiki/open-questions.md. - If it resolved an existing open question, fold it in and mark that question Resolved with a pointer.
- Update
wiki/index.mdif you added a page.
4. Log + commit (only if the wiki changed)
- If you wrote anything back, append a
## [YYYY-MM-DD] query | <topic>entry tolog.mdand commit (push if a remote is configured). - A pure lookup that changed nothing needs no log entry.
Guardrail
Don't let "file it back" bloat the wiki. A one-off factual lookup stays in the conversation; only durable synthesis earns a page.
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 · 50 lines · 85 tokens per session scan A b66435355778
wiki-query is a skill published in the GitHub repository shrimbly/project-wiki (6 stars, last pushed 3mo ago), licensed MIT. It adds 85 tokens to every session and 520 once invoked, about $0.0003 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…