A tool for finding and navigating a Markdown knowledge base, including linked notes, metadata, relationships, backlinks, and repository context. It loads the instructions and information relevant to a particular file or project.

Use it to search notes, find related or linking documents, inspect metadata and graph reports, and load repository-specific guidance and prior decisions.

It reduces the need to search every note manually and helps agents use the right project context before answering questions or making changes.

query-kb — Skill by hraness

Install

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.

agentmods

npx agentmods add skills/hraness/atet/query-kb

Any agent

npx skills add hraness/atet --skill query-kb

Clone the repo

git clone --depth 1 https://github.com/hraness/atet

Made for: Claude Code, Codex.

Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,472 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00083	$0.02472
Opus 5	$0.00042	$0.01236
Sonnet 5	$0.00017	$0.00494
Haiku 4.5	$0.00008	$0.00247

Measured 3d ago against content hash 982eea60ef02, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

query-kb 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 3d 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.

Origin

This is a copy

100% identical to query-kb — 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.

.agents/skills/query-kb/SKILL.md · 206 lines

How it starts

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

Query the knowledge base

Use the cheapest precise view first, then broaden. Markdown files remain the authority; search scores, metadata rows, and graph results are derived views.

Locate the vault

Resolve <vault> to the directory containing its managed or authored index.md, then set the shell-local KB_ROOT to that path (KB_ROOT=kb from a typical repository root, or KB_ROOT=. from inside the vault).
Resolve <repository> to the repository root when the question concerns a repository path (KB_REPO=. from that root).
Read the vault's applicable agent instructions and note conventions.
Pass the resolved path to every --root; do not scan a repository root merely because that is where the agent session started.

Choose the retrieval lane

Repository file or directory: run kb context first. Read its inherited guides root to nearest, then inspect its maintained knowledge, active plans, dated research, reports, and separate historical-plan group. Open only useful context hubs or records.
Known frontmatter field or tag such as type, status, or area: use kb list.
Known note title, path, or alias: use kb links or kb backlinks, which resolve note identities before returning authored relationships.
A whole-vault structural question or relationship audit: use kb graph --json, then inspect the smallest relevant portion of its canonical output.
A phrase, identity, or concept expressed with different vocabulary: use kb search, whose default hybrid result preserves exact and QMD evidence separately.
Direct provenance for one note or repository path: use kb history or kb history search without changing authored metadata or links.
Recent captures awaiting maintained disposition: use the advisory kb inbox view.
Broad orientation: read index.md, then follow the smallest useful link trail. Use kb catalog when an exhaustive disposable inventory is actually needed.

kb context src/parser.ts --root "$KB_ROOT" --repo "$KB_REPO"
kb list --root "$KB_ROOT" --scope src/parser --where type=plan --json
kb list --root "$KB_ROOT" --where type=plan --where status=in-progress --sort area --json
kb list --root "$KB_ROOT" --tag retrieval --sort title --json
kb backlinks "Plan title or path" --root "$KB_ROOT" --json
kb links "Plan title or path" --root "$KB_ROOT" --direction both --depth 1 --limit 25 --json
kb relation list "Plan title or path" --root "$KB_ROOT" --json
kb graph --root "$KB_ROOT" --json
kb search "why browser capture uses the current tab" --root "$KB_ROOT" --json
kb search "accepted ingestion plans" --root "$KB_ROOT" --where type=plan --where status=accepted --tag ingestion --json
kb search "notes/write-path" --root "$KB_ROOT" --mode exact --no-history --json
kb history "notes/write-path" --root "$KB_ROOT" --repo "$KB_REPO" --json
kb history search src/parser.ts --root "$KB_ROOT" --repo "$KB_REPO" --json
kb inbox --root "$KB_ROOT" --limit 25 --json

Read the full file on GitHub · 206 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

3d ago First seen · 206 lines · 83 tokens per session scan A 982eea60ef02

Subscribe to this mod's changes

query-kb is a skill published in the GitHub repository hraness/atet (4 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 2,472 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 query-kb, differing in 0 lines, and is treated as a copy.

Memory and context bun cli diagrams image-generation local-first

ima2

Use the ima2-gen CLI/server to generate, edit, inspect, and manage local AI image generation jobs.

lidge-jun/ima2-gen · 25 tokens

ima2-front

Frontend implementation skill for ima2 users. Use for any frontend, web UI, or visual implementation work — building, styling, or redesigning pages/components, responsive layouts, motion, component architecture, and production-surface polish. Pairs with ima2-uiux: load it first when design direction is vague; this…

lidge-jun/ima2-gen · 149 tokens

ima2-uiux

Design direction discovery and UX judgment for ima2 users. Use for UI/UX direction and design judgment — vague visual briefs, onboarding, empty/error/loading states, layout vocabulary, typography breaks, favicons, logos, and brand identity choices. Pairs with ima2-front: this skill decides the design direction, then…

lidge-jun/ima2-gen · 118 tokens

query-kb