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/darkcodepe/brainstem/wiki-querynpx skills add DarkCodePE/brainstem --skill wiki-querygit clone --depth 1 https://github.com/DarkCodePE/brainstemWhat 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.00010 | $0.00381 |
| Opus 5 | $0.00005 | $0.00191 |
| Sonnet 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 yesterday.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 10 tokens to every session and 381 once invoked, about $0.0001 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
gpt-researcher
GPT Researcher is an autonomous deep research agent that conducts web and local research, producing detailed reports with citations. Use this skill when helping developers understand, extend, debug, or integrate with GPT Researcher - including adding features, understanding the architecture, working with the API…
gpt-researcher
Autonomous deep research from Codex via MCP.
bilibili_search
Search for videos on Bilibili using keyword queries generated from user interests.
site-config-creation
Create or update the [site] section of stencila.toml for published Stencila sites. Use when asked to configure site domain, title, author, logo, icons, labels, descriptions, socials, featured content, navigation, routes, access, layout presets and regions, glide, search, formats, reviews, uploads, remotes, actions…
wiki_submit
Submit wiki documentation pages to Wegent backend API. Simplifies the HTTP POST process for wiki content submission.
task-search
在框架预查的候选 bot 集里决出执行者(who)与协作方式(how),返回 4 态 SearchResult(HITSINGLE/HITGROUP/HITMULTIBOTS/MISS)。对齐案例剧本确定式映射。.