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/contacttam/q-command-system/q-verifygit clone --depth 1 https://github.com/contactTAM/q-command-systemWrote 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/contacttam/q-command-system/q-verify)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-verify"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-verify.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.00006 | $0.00475 |
| Opus 5 | $0.00003 | $0.00237 |
| Sonnet 5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
q-verify 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 4d 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
Verify Session Files
Purpose: Check that /q-end, /q-checkpoint, or /q-save worked correctly.
Step 1: Check Transcripts
ls -la .q-system/transcripts/*$(date +%Y-%m-%d)* 2>/dev/null
For each file found:
- Show filename
- Show creation time
- Show line count:
wc -l [file]
Step 2: Check Session Notes
ls -la .q-system/session-notes/*$(date +%Y-%m-%d)* 2>/dev/null
For each file found:
- Show filename
- Show creation time
- Show line count
Step 3: Check Checkpoints
ls -la .q-system/checkpoints/*$(date +%Y-%m-%d)* 2>/dev/null
List all checkpoints from today with times.
Step 4: Check Git Status
git status
git log -1 --format="%h %s (%cr)"
Show:
- Clean working tree or uncommitted changes
- Last commit hash, message, and time
Step 5: Report
=== Verification Report ===
Transcripts:
[Found/None] .q-system/transcripts/[filename]
- Created: [time]
- Size: [N] lines
Session Notes:
[Found/None] .q-system/session-notes/[filename]
- Created: [time]
- Size: [N] lines
Checkpoints:
[N] checkpoint(s) from today:
- [filename] ([time])
Git:
- Working tree: [clean/dirty]
- Last commit: [hash] "[message]" ([time])
- Ahead of origin: [N] commit(s)
Status: [All Clear / Issues Detected]
[If issues, list what's missing or problematic]
When to use:
- After /q-end to confirm it worked
- After /q-checkpoint to verify save
- After /q-save to see what was captured
- When resuming to see what exists from previous work
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.
- 4d ago First seen · 87 lines · 6 tokens per session scan A 3a5900995c52
q-verify is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 475 once invoked, about $0.0000 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 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.