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 DarkCodePE/brainstem --skill wiki-querygit clone --depth 1 https://github.com/DarkCodePE/brainstemWrote 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/darkcodepe/brainstem/wiki-query)<a href="https://agentmods.dev/skills/darkcodepe/brainstem/wiki-query"><img src="https://agentmods.dev/badge/skills/darkcodepe/brainstem/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/darkcodepe/brainstem/wiki-query"><img src="https://agentmods.dev/badge/skills/darkcodepe/brainstem/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.00010 | $0.00381 |
| Opus 5.5 | $0.00004 | $0.00152 |
| Sonnet 5.5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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
Search the wiki and synthesise a grounded answer with citations.
Steps
- Search
wiki/index.mdfor relevant pages matching the question - Read the top matching pages (up to max_pages)
- Synthesise an answer grounded in wiki content
- Cite every factual claim with
(source: wiki/path/to/page.md) - Optionally file the answer at
wiki/answers/<slug>.md
Error handling
- If no relevant pages found, return NO_RELEVANT_PAGES error
- Never hallucinate information not present in the wiki
- Clearly state gaps when wiki coverage is partial
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 · 57 lines · 10 tokens per session scan A fae4cccec8de
wiki-query is a skill published in the GitHub repository DarkCodePE/brainstem (1 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 381 once invoked, about $0.0000 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
solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.
query-enhancer
RAG query optimization - rewrite, expand, decompose, and analyze search queries for better retrieval results.
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.
wiki-import
Import a wiki graph into the current vault from graph.json or an OKF/markdown bundle. Use for transferring previously exported wiki content between vaults; pair with wiki-export for the reverse direction.