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.
git 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-upgrade)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-upgrade"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-upgrade/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-upgrade"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-upgrade.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.01929 |
| Opus 5.5 | $0.00003 | $0.00772 |
| Sonnet 5.5 | $0.00002 | $0.00386 |
| Haiku 4.5 | $0.00001 | $0.00193 |
Grade A, and why
q-upgrade 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 2mo 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Q-Command System
Purpose: Efficiently check and upgrade to the latest Q-Command System version.
Efficiency: This command uses a script-based approach that reduces token usage by ~85% compared to individual file fetches.
MANDATORY PRE-FLIGHT CHECKLIST
STOP. Before proceeding, confirm:
- 1. I will check versions BEFORE making changes
- 2. I will get explicit user permission before upgrading
- 3. I will use the upgrade SCRIPT (not individual WebFetch calls)
- 4. I will verify the upgrade completed successfully
Step 1: Check Local Version
1.1 Read Local Version Info
cat .q-system/version.yaml 2>/dev/null || cat .q-system/version 2>/dev/null || echo "No version file found"
- Command executed
- Local version identified: ____________________
Parse the version:
- If
version.yaml: Look forq_system.version - If
versionfile: Single line with version number - If neither: Assume pre-2.1 installation
1.2 Check for releases.yaml (if exists locally)
cat .q-system/releases.yaml 2>/dev/null | head -5 || echo "No local releases.yaml"
VERIFICATION GATE 1:
Local installation:
- Version: [version or "unknown"]
- Version file type: [version.yaml / version / none]
Step 2: Fetch Remote Version Info
2.1 Fetch releases.yaml (Small File - Efficient)
Use WebFetch to get:
https://raw.githubusercontent.com/contactTAM/q-command-system/main/templates/releases.yaml
- Fetch attempted
- Latest version identified: ____________________
- Commands changed since local version: ____________________
2.2 Parse Release Information
From releases.yaml, identify:
current_version: The latest available version- Find releases between local version and current version
- Aggregate
commands_changedfrom all intermediate releases - Note any
breaking_changesormigration_notes
VERIFICATION GATE 2:
Version comparison:
- Local version: [local]
- Latest version: [remote]
- Status: [Up to date / Upgrade available]
- Commands changed: [list or "all"]
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.
- 2mo ago First seen · 356 lines · 8 tokens per session scan E 1ee7e682eacc
q-upgrade is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 1,929 once invoked, about $0.0000 per session on Opus 5.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
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.