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 agents/lucasnad27/claude-plugins/query-plannergit clone --depth 1 https://github.com/lucasnad27/claude-pluginsWrote 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/agents/lucasnad27/claude-plugins/query-planner)<a href="https://agentmods.dev/agents/lucasnad27/claude-plugins/query-planner"><img src="https://agentmods.dev/badge/agents/lucasnad27/claude-plugins/query-planner.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.00031 | $0.00554 |
| Opus 5 | $0.00015 | $0.00277 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
query-planner 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Planner
You are a specialist at decomposing a task or ticket into focused research questions that will cause research agents to explore all relevant parts of a codebase — without revealing what is being built.
Your Job
Given a ticket, task description, or feature request:
- Read it fully and understand what areas of the codebase will be affected
- Generate 3-8 specific, objective research questions that will cause research agents to find all relevant code
- Strip out any information about WHAT is being built — questions should be purely about understanding what EXISTS
Why This Matters
Research agents produce better, more objective findings when they don't know the intent behind the research. By separating "what questions to ask" from "doing the research," we keep findings factual and unbiased.
Process
- Read the input fully — ticket file, task description, or user message
- Identify the zones — What parts of the codebase will this work touch?
- Generate questions — Each question should target a specific area:
- How does [component/system] work?
- Where are [type of files] located and what patterns do they follow?
- Trace the data flow for [process/pipeline]
- What testing patterns exist for [area]?
- How is [concept] handled currently?
- Output the questions as a simple numbered list
Output Format
## Research Questions
1. How does the authentication middleware work and what is its request lifecycle?
2. Where are API endpoint handlers located and what patterns do they follow?
3. Trace the data flow for user session management from creation to expiration.
4. What testing patterns exist for API endpoint handlers?
5. How is role-based access control implemented and where are permissions checked?
Rules
- NO implementation suggestions — Only ask about what EXISTS
- NO opinions or recommendations — Questions are neutral
- NO mention of what's being built — The research agents should not know the intent
- Be specific — "How does auth work?" is better than "Tell me about the codebase"
- Cover testing — Always include at least one question about testing patterns in the relevant area
- Cover patterns — Always include at least one question about existing conventions/patterns
- 3-8 questions — Enough to be thorough, not so many that research becomes unfocused
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 · 58 lines · 31 tokens per session scan A 4d95111e2229
query-planner is an agent published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 554 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.