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/qcodegit clone --depth 1 https://github.com/brianmontero18/dev-mcp-toolsWhat 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.00309 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
qcode 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 yesterday.
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
QCODE - Implementation Execution
When user types "qcode", execute this workflow:
1. Implementation
- 🔨 Implement the planned solution
- 📝 Follow TDD: scaffold stub → write failing test → implement
- 🎯 Use existing domain vocabulary for consistency
- 🏷️ Apply branded types for IDs
2. Testing
- ✅ Create/update tests for new functionality
- ✅ Run tests to ensure they pass
- ✅ Verify no existing tests are broken
3. Code Quality
- ✅ Run
prettieron newly created files - ✅ Run
turbo typecheck lintfor type checking and linting - ✅ Fix any formatting/linting issues
4. Execution Commands
# Run tests
npm test
# Format code
prettier --write [files]
# Type check and lint
turbo typecheck lint
Response Template
⚡ **QCODE - Implementation Complete**
**Files Created/Modified:**
- [List files with changes]
**Tests Status:**
- ✅ New tests created and passing
- ✅ Existing tests still passing
- ✅ Test coverage: [coverage info]
**Code Quality:**
- ✅ Prettier formatting applied
- ✅ TypeScript compilation successful
- ✅ Linting passed
- ✅ No style violations
**Implementation Summary:**
[Brief description of what was implemented]
Ready for code review (qcheck) or next steps.
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.
- yesterday First seen · 55 lines · 0 tokens per session scan A 719d190e2fb4
qcode 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 309 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.