agentmods.dev

knowledge-query

knowledge-query is a skill for Claude Code from cogni-work/insight-wave. It costs 124 tokens per session (4,999 once invoked), scanned A, original, Apache-2.0.

A read-only question-answering guide for a connected knowledge base, which is a collection of stored reference pages. It finds relevant pages, reads them, and produces an answer with citations from those pages.

In plain words
What is it for?
Use it to ask one focused question about a bound wiki, review the pages supporting the answer, and see which knowledge base and evidence level were used.
Why use it?
It provides a quick answer grounded in the available internal documentation without searching the web or pretending the knowledge base covers more than it does.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cogni-knowledge plugin — 23 skills, 16 agents shipped together

not rated 13repo changed 1mo ago A scan 124 tokens original Apache-2.0

Good fit Use it to ask one focused question about a bound wiki, review the pages supporting the answer, and see which knowledge base and evidence level were used.

Compare 6 skills from other repositories ↓
View source ↗ cogni-work/insight-wave
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add cogni-work/insight-wave
Claude Code
/plugin install cogni-knowledge

Made for: Claude Code.

Or install cogni-knowledge, the plugin that ships this one along with the rest of its 23 skills, 16 agents.

Wrote 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.

agentmods badge for knowledge-query

README.md
[![agentmods](https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-query/github.svg)](https://agentmods.dev/skills/cogni-work/insight-wave/knowledge-query)
Your own site
<a href="https://agentmods.dev/skills/cogni-work/insight-wave/knowledge-query"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-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.

agentmods 80×15 button for knowledge-query

Your own site · 80×15
<a href="https://agentmods.dev/skills/cogni-work/insight-wave/knowledge-query"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,999 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00124 $0.04999
Opus 5.5 $0.00050 $0.02000
Sonnet 5.5 $0.00025 $0.01000
Haiku 4.5 $0.00012 $0.00500

Measured 1mo ago against content hash 3e9af5998810, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

knowledge-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.

cogni-knowledge/skills/knowledge-query/SKILL.md · 340 lines

How it starts

The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Knowledge Query

Ask a question against a bound cogni-knowledge base. This skill is the shallow rung of the query↔research depth ladder: it ranks the pages that cover the question, reads them, and synthesizes a grounded, cited answer — one question, index-first, ≤12 pages, no web, no verify (the deep wiki-only report rung is owned by knowledge-compose --source wiki).

It runs natively on the vendored wiki engine — it consumes the shared wiki-grounding.py discovery primitive directly and reads the wiki pages with the Read tool, so a Karpathy base answers questions without cogni-wiki installed. The cogni-knowledge value-add:

  1. Binding-aware wiki path resolution — no --wiki-root from the user; read from binding.json.
  2. Index-first grounded synthesis — rank covering pages via wiki-grounding.py, read them, answer only from what they say (with [[slug]] citations), and report honestly when coverage is thin.
  3. Knowledge-base footer — every answer ends with one line tying it to the knowledge slug + deposit count + fetch-cache health, so the user remembers where the answer came from and how much evidence the base holds.

Read ${CLAUDE_PLUGIN_ROOT}/references/differentiation-thesis.md once per session to anchor on the accumulation thesis. The synthesis discipline below — answer only from the pages you read, cite every claim, admit uncertainty — is the shallow rung's core contract.

When to run

  • User asks a question and references a knowledge base by slug — "what does my eu-ai-act base know about X?", "query the eu-ai-act base on Article 6"
  • User explicitly invokes /cogni-knowledge:knowledge-query
  • User asks a question that clearly lives in a bound knowledge base's domain after knowledge-resume has shown what is in the base

Never run when

  • No binding.json exists at the resolved knowledge root — route the user to /cogni-knowledge:knowledge-setup first.
  • The user wants a deep, multi-section, web-verified report rather than a single grounded answer — that is knowledge-compose --source wiki (the deep rung), not this skill.

Read the full file on GitHub · 340 lines

Changes

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.

  1. 1mo ago Changed · -13 lines 3e9af5998810
  2. 1mo ago First seen · 353 lines · 124 tokens per session scan A a3460677f064

Subscribe to this mod's changes

knowledge-query is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 124 tokens to every session and 4,999 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-30.

Research
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens