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/qgitgit 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.00432 |
| Opus 5 | $0.00000 | $0.00216 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
qgit 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
QGIT - Git Workflow Automation
When user types "qgit", execute this workflow:
1. Git Operations
- ✅ Add all changes to staging:
git add . - ✅ Create commit with proper message
- ✅ Push to remote branch
2. Commit Message Rules (Conventional Commits)
- ✅ Format:
<type>[optional scope]: <description> - ✅ NO Claude/Anthropic references
- ✅ Types:
feat:- new feature (MINOR version)fix:- bug patch (PATCH version)BREAKING CHANGE:- breaking API change (MAJOR version)build:,chore:,ci:,docs:,style:,refactor:,perf:,test:
3. Execution Commands
# Stage all changes
git add .
# Create commit
git commit -m "type(scope): description
Optional body explaining the changes.
Optional footer with breaking changes or issue refs."
# Push to remote
git push origin [current-branch]
4. Commit Message Examples
feat: add user authentication system
fix: resolve login validation error
docs: update API documentation
refactor: simplify data processing logic
test: add unit tests for user service
chore: update dependencies
Response Template
📤 **QGIT - Git Workflow Complete**
**Changes Staged:**
- [List modified/added files]
**Commit Message:**
type: [description]
[Optional body explaining changes]
**Git Operations:**
- ✅ `git add .` - All changes staged
- ✅ `git commit -m "..."` - Commit created
- ✅ `git push origin [branch]` - Pushed to remote
**Commit Hash**: [commit-hash]
**Branch**: [branch-name]
**Remote URL**: [repo-url]
Ready for PR creation or next development cycle.
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 · 69 lines · 0 tokens per session scan A 55d800919206
qgit 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 432 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.