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/davidroliverba/architectkb/graph-querynpx skills add DavidROliverBA/ArchitectKB --skill graph-querygit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/graph-query)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/graph-query"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/graph-query.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01393 |
| Opus 5 | $0.00000 | $0.00696 |
| Sonnet 5 | $0.00000 | $0.00279 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
graph-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/graph-query
Query the vault's knowledge graph index using natural language or structured queries.
Usage
/graph-query ADRs with status proposed
/graph-query high priority tasks
/graph-query orphaned notes
/graph-query broken links
/graph-query backlinks to Project - MyProject
/graph-query --type=Adr --status=accepted
Instructions
When the user invokes /graph-query or asks to query the graph index:
Phase 1: Ensure Index Exists
Before executing any query, check if the graph index exists:
-
Check if
.graph/index.jsonexists -
If not found, inform the user and offer to build it:
The graph index needs to be generated first. Running: npm run graph:buildExecute:
npm run graph:build -
If index exists but is stale (>1 day old), optionally suggest rebuilding
Phase 2: Parse the Query
Understand what the user is asking for. The query system supports:
Natural Language Patterns:
| Pattern | Interpretation |
|---|---|
| "ADRs with status proposed" | --type=Adr --status=proposed |
| "high priority tasks" | --type=Task --priority=high |
| "active projects" | --type=Project --status=active |
| "orphaned notes" | --orphans |
| "broken links" | --broken-links |
| "stale notes" | --stale |
| "meetings about kafka" | --type=Meeting --search=kafka |
| "backlinks to X" | --backlinks="X" |
| "notes mentioning aws" | --search=aws |
Structured Parameters:
| Parameter | Description | Example |
|---|---|---|
--type= |
Filter by note type | --type=Adr, --type=Project |
--status= |
Filter by status | --status=proposed, --status=active |
--priority= |
Filter by priority | --priority=high |
--search= |
BM25 relevance search (ranked results) | --search="kafka integration" |
--backlinks= |
Find notes linking to target | --backlinks="Project - MyProject" |
--orphans |
List orphaned notes | |
--broken-links |
List broken wiki-links | |
--stale |
List notes >6 months old | |
--stats |
Show index statistics | |
--json |
Output as JSON with scores |
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.
- 4d ago First seen · 198 lines · 0 tokens per session scan A b8816bbd521d
graph-query is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,393 tokens. 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…