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 CarbeneAI/Forge --skill wiki-querygit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/wiki-query)<a href="https://agentmods.dev/skills/carbeneai/forge/wiki-query"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/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/carbeneai/forge/wiki-query"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/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.00089 | $0.01226 |
| Opus 5 | $0.00044 | $0.00613 |
| Sonnet 5 | $0.00018 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00123 |
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 8d 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.
This is a copy
100% identical to wiki-query — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-query: Query the Wiki
The wiki has already done the synthesis work. Read strategically, answer precisely, and file good answers back so the knowledge compounds.
Query Modes
Three depths. Choose based on the question complexity.
| Mode | Trigger | Reads | Token cost | Best for |
|---|---|---|---|---|
| Quick | query quick: ... or simple factual Q |
hot.md + index.md only | ~1,500 | "What is X?", date lookups, quick facts |
| Standard | default (no flag) | hot.md + index + 3-5 pages | ~3,000 | Most questions |
| Deep | query deep: ... or "thorough", "comprehensive" |
Full wiki + optional web | ~8,000+ | "Compare A vs B across everything", synthesis, gap analysis |
Quick Mode
Use when the answer is likely in the hot cache or index summary.
- Read
wiki/hot.md. If it answers the question, respond immediately. - If not, read
wiki/index.md. Scan descriptions for the answer. - If found in index summary, respond and do not open any pages.
- If not found, say "Not in quick cache. Run as standard query?"
Do not open individual wiki pages in quick mode.
Standard Query Workflow
- Read
wiki/hot.mdfirst. It may already have the answer or directly relevant context. - Read
wiki/index.mdto find the most relevant pages (scan for titles and descriptions). - Read those pages. Follow wikilinks to depth-2 for key entities. No deeper.
- Synthesize the answer in chat. Cite sources with wikilinks:
(Source: [[Page Name]]). - Offer to file the answer: "This analysis seems worth keeping. Should I save it as
wiki/questions/answer-name.md?" - If the question reveals a gap: say "I don't have enough on X. Want to find a source?"
Deep Mode
Use for synthesis questions, comparisons, or "tell me everything about X."
- Read
wiki/hot.mdandwiki/index.md. - Identify all relevant sections (concepts, entities, sources, comparisons).
- Read every relevant page. No skipping.
- If wiki coverage is thin, offer to supplement with web search.
- Synthesize a comprehensive answer with full citations.
- Always file the result back as a wiki page. Deep answers are too valuable to lose.
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.
- 8d ago First seen · 165 lines · 89 tokens per session scan A 6f0e242485dd
wiki-query is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,226 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to wiki-query, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
knowledge-management
../../../governance/knowledge-management/SKILL.md.
analyzing-memory-forensics-with-lime-and-volatility
Performs Linux memory acquisition using LiME (Linux Memory Extractor) kernel module and analysis with Volatility 3 framework. Extracts process lists, network connections, bash history, loaded kernel modules, and injected code from Linux memory images. Use when performing incident response on compromised Linux systems.
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…