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/lestrrat-ai/claude-code-plugins/query-apinpx skills add lestrrat-ai/claude-code-plugins --skill query-apigit clone --depth 1 https://github.com/lestrrat-ai/claude-code-pluginsWhat 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.00065 | $0.00777 |
| Opus 5 | $0.00032 | $0.00388 |
| Sonnet 5 | $0.00013 | $0.00155 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
query-api 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 2d 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
Query Fusion API
Invocation: Claude Code /fusion:query-api; Codex $fusion:query-api.
-
Resolve
scripts/query_fusion_api.pyfrom this activeSKILL.mdto an absolute path. NEVER use a plugin-root environment variable. -
Run one subcommand per question:
["python3", "<absolute-query_fusion_api.py>", "<subcommand>", "<argument>"]Question Subcommand Provenance and counts for the database in use infoFind names matching a term search <term>Full detail for a class, function, or one member show <name>All members of a class members <class>(--owndrops inherited ones)Base chain + direct subclasses tree <class>Which symbols' docs mention a term doc-search <term>showaccepts qualnames (adsk.fusion.ExtrudeFeatures), bare class names,Class.member, and bare member names; ambiguous input returns the candidate list — pick one and re-run.Member lookups include inherited members by default, and every one is reported against the class that declares it:
show Class.memberresolves a member declared on any base,show Classlists inherited members after the class's own, andmembers <class>groups them by declaring class. The bases are walked in the order Python itself resolves an attribute, so the class reported is the class the member really comes from.membersandtreetake a class; given anything else they report no such class. -
Database resolution order (explicit
--db, then user cache, then the bundled copy) is owned by the script's module docstring; pass--dbonly when the user names a database, and pass it before the subcommand — after it, it is a usage error and exits 2:["python3", "<absolute-query_fusion_api.py>", "--db", "<path>", "<subcommand>", "<argument>"]Database missing at every location → tell user to run
/fusion:compile-api(Codex$fusion:compile-api). -
Answer from script output only. Exit code 1 with a candidate list or "no matches" on stdout is a lookup miss, not a failure — refine the name and re-run, or report the miss. Exit code 1 with an
error:line on stderr is a real failure — relay it and stop. The causes are: no database; the file is not one; a database that opened but could not answer the subcommand (could not answer '<subcommand>'); and a class whose recorded bases have no consistent resolution order, which is refused rather than answered from a guessed order and names the class. The last two are defects in the database — report them as such, and recompile with/fusion:compile-api(Codex$fusion:compile-api).
Read-only. The bundled database ships with the plugin; NEVER edit or regenerate it here — regeneration
is compile-api's job.
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.
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.
- 2d ago First seen · 57 lines · 65 tokens per session scan A fc6fb9a37671
query-api is a skill published in the GitHub repository lestrrat-ai/claude-code-plugins (18 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 777 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…