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 hogu-dev/llmkb --skill kb-querygit clone --depth 1 https://github.com/hogu-dev/llmkbWrote 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/hogu-dev/llmkb/kb-query)<a href="https://agentmods.dev/skills/hogu-dev/llmkb/kb-query"><img src="https://agentmods.dev/badge/skills/hogu-dev/llmkb/kb-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/hogu-dev/llmkb/kb-query"><img src="https://agentmods.dev/badge/skills/hogu-dev/llmkb/kb-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.00050 | $0.00384 |
| Opus 5.5 | $0.00020 | $0.00154 |
| Sonnet 5.5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
kb-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
kb-query
Answer a question from one or more llmkb knowledge bases, cite what you used,
and — when the answer produced durable new knowledge — file it back.
When to use
A user asks a question that the KB(s) should be able to answer, or asks you to research within them.
Steps
- Route via the index first. Read
wiki/index.md(each KB's) — one line per page — to find the pages most likely to hold the answer. For multiple KBs, read each index; results are tagged by KB name. - Search at scale. If the index is large or routing is unclear, run
llmkb search "<query>" --kb <dir>(repeat--kbfor several KBs). Use the hits to pick pages. - Read the pages you selected and compose the answer.
- Cite every page you drew on by its
[[Title]]. - Compound (optional but encouraged). If answering produced durable new
synthesis not already captured, write it as a
conceptpage (emptysources= agent-authored), then runllmkb reindex, append a## [YYYY-MM-DD] synthesis | <title>line towiki/log.md, and runllmkb lint.
Done when
The question is answered with page citations, and any new synthesis is filed, indexed, logged, and lint-clean.
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 · 36 lines · 50 tokens per session scan A 714c8f1c0e02
kb-query is a skill published in the GitHub repository hogu-dev/llmkb (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 384 once invoked, about $0.0002 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
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
recursive-decomposition
Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered…
design-tokens
This skill should be used when a user wants to scaffold or refactor a design token system — e.g. "set up design tokens", "create a design system foundation", "extract these hardcoded colors into tokens", "add a type scale", "theming setup", or "dark mode tokens". It produces a single source of truth for color, type…
slice
Turn a feature into well-defined, independently shippable slices — whether it's an epic that needs breaking apart or a single story that needs sharpening into a job story.
standup
Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.