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 commands/brianmontero18/dev-mcp-tools/qplangit clone --depth 1 https://github.com/brianmontero18/dev-mcp-toolsWrote 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/commands/brianmontero18/dev-mcp-tools/qplan)<a href="https://agentmods.dev/commands/brianmontero18/dev-mcp-tools/qplan"><img src="https://agentmods.dev/badge/commands/brianmontero18/dev-mcp-tools/qplan.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.00315 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
qplan 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.
What it actually says
QPLAN - Codebase Analysis & Planning
When user types "qplan", execute this workflow:
1. Codebase Analysis
- 🔍 Analyze similar parts of the codebase
- 📋 Review existing patterns and conventions
- 🧩 Identify reusable components/utilities
- 📐 Check architectural consistency
2. Plan Validation
Determine whether your plan:
- ✅ Consistency: Follows existing codebase patterns
- ✅ Minimal changes: Introduces least possible modifications
- ✅ Code reuse: Leverages existing functions/components
- ✅ Architecture: Maintains current system design
3. Tools to Use
Grep- Find similar implementationsGlob- Locate related filesRead- Study existing code patterns
Response Template
📋 **QPLAN - Codebase Analysis Complete**
**Similar Implementations Found:**
- [List similar features/patterns found]
**Existing Components to Reuse:**
- [List reusable utilities/components]
**Plan Consistency Check:**
- ✅ Consistent with codebase: [explanation]
- ✅ Minimal changes: [what will be modified]
- ✅ Code reuse: [what existing code will be leveraged]
- ✅ Architecture: [how it fits current design]
**Implementation Plan:**
1. [Step 1]
2. [Step 2]
3. [Step 3]
**Files to Modify/Create:**
- [List files with brief description of 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 · 46 lines · 0 tokens per session scan A 88bd3acfdb20
qplan is a command published in the GitHub repository brianmontero18/dev-mcp-tools (0 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 315 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-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.