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-compactgit 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-compact)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-compact"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-compact.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.00010 | $0.00399 |
| Opus 5 | $0.00005 | $0.00199 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
q-compact 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 3d 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
Safe Compact
Purpose: Free up context space by saving a checkpoint first, then compacting. Protects your work while giving more room to continue.
Why Use /q-compact Instead of /compact Directly
/compactalone summarizes and loses detail/q-compactsaves a checkpoint FIRST, then compacts- Your detailed work history is preserved in the checkpoint file
- You get more context space AND keep your work safe
Step 1: Create Checkpoint
Execute /q-checkpoint to save current progress.
Wait for confirmation that checkpoint was saved.
Step 2: Run Compact
Tell the user:
Checkpoint saved. Now run this command:
/compact Preserve: key decisions, files changed, current task status. This is a /q-compact operation - checkpoint already saved.
Or if you can execute /compact directly, do so with that prompt.
Step 3: Report Results
/q-compact complete!
Checkpoint saved: .q-system/checkpoints/[filename]
Context compacted: More space available
Your detailed work is preserved in the checkpoint.
/q-end will merge checkpoint + remaining work into complete session notes.
Tip: Run /context to see your new context usage.
When to use:
- Context usage above 70%
- After /context shows high usage
- Before starting a large new task
- When Claude's responses are getting slower
Example workflow:
[Working for 90 minutes, context getting full]
User: /context → Shows 75% usage
User: /q-compact → Saves checkpoint, then compacts
→ Now at ~30% usage
[Continue working with fresh context]
User: /q-end → Merges checkpoint + new 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.
- 3d ago First seen · 66 lines · 10 tokens per session scan A 6f4472ee3543
q-compact is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 399 once invoked, about $0.0001 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.