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-setup)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-setup"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-setup/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-setup"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-setup.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.02171 |
| Opus 5.5 | $0.00003 | $0.00868 |
| Sonnet 5.5 | $0.00002 | $0.00434 |
| Haiku 4.5 | $0.00001 | $0.00217 |
Grade A, and why
q-setup 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Purpose: One smart command to set up or reconfigure Q-Command System based on your project's context.
MANDATORY PRE-FLIGHT CHECKLIST
STOP. Before proceeding, confirm:
- 1. I will detect context BEFORE asking questions
- 2. I will create version.yaml with provenance information
- 3. I will VERIFY all created files
- 4. I will NEVER delete user's existing work
Step 1: Detect Context
1.1 Check for Existing Installation
ls -la .q-system/ 2>/dev/null || echo "No .q-system folder"
ls -la .q-system/version.yaml 2>/dev/null || echo "No version.yaml"
ls -la .q-system/config.md 2>/dev/null || echo "No config.md"
- Checked for .q-system folder
- Checked for version.yaml
- Checked for config.md
Decision logic:
- NO .q-system/: → New Setup (Step 2)
- .q-system/ exists with config: → Existing Setup (Step 3)
Step 2: New Setup
Display to user:
=== Q-Command System Setup ===
I'll configure Q-System for your project. How detailed do you want setup to be?
1. Quick (2-3 minutes)
- Basic questions, smart defaults
- Good for simple projects or getting started fast
2. Detailed (10-15 minutes)
- Domain-specific questions, full configuration
- Good for serious projects needing maximum customization
Which would you prefer? [1/2]:
- Options presented
- User choice recorded: ____________________
Quick Mode (Option 1)
Ask these 4 essential questions:
Q1: What kind of project is this?
- Software/Code
- Writing (book, screenplay, content)
- Research/Academic
- Business/Planning
- Other: [describe]
Q2: Are you working solo or with others?
- Solo
- With collaborators (need multi-user file naming)
Q3: What's your experience level with this type of project?
- Beginner (more guidance helpful)
- Intermediate (some guidance)
- Advanced (minimal guidance)
Q4: Anything special I should know about your project?
- [Free text, optional]
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 · 385 lines · 8 tokens per session scan A de76a049f1c7
q-setup 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 2,171 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.