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-status)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-status"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-status/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-status"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-status.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.00005 | $0.00688 |
| Opus 5.5 | $0.00002 | $0.00275 |
| Sonnet 5.5 | $0.00001 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
q-status 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Status
Purpose: Display current session state, progress, and recommendations.
Step 1: Gather Information
- Check for checkpoint files from today:
ls .q-system/checkpoints/*$(date +%Y-%m-%d)* 2>/dev/null - Check git status:
git status --short - Count uncommitted files
- Estimate session duration (if start time known)
Step 2: Display Status
=== Session Status ===
Session: [Started time] ([X] hours [Y] minutes ago)
Participant: [Name]
Type: [Regular / Continued from auto-compact]
Progress:
- Accomplishments: [N] major items
- Files modified: [N]
- Key decisions: [N]
Checkpoints:
- Last checkpoint: [time] ([X] minutes ago)
- Location: .q-system/checkpoints/[filename]
[or "None yet"]
Git Status:
- Uncommitted changes: [Yes/No] ([N] files)
- Last commit: [message] ([time] ago)
Context Health:
- Estimated usage: ~[XX]%
- Status: [Healthy / Caution / Warning / Critical]
- Time since checkpoint: [X] minutes
Recommendations:
[Based on status, show relevant recommendations]
Context Health Thresholds
| Usage | Status | Recommendation |
|---|---|---|
| 0-70% | Healthy | Continue normally |
| 70-85% | Caution | Consider /q-checkpoint soon |
| 85-90% | Warning | /q-checkpoint NOW |
| 90%+ | Critical | Use /q-save, /q-end may fail |
Step 3: Recommendations Logic
Show relevant recommendations based on context and session state:
Context-based (highest priority):
-
If context 90%+: "CRITICAL: Use /q-save immediately. /q-end may fail at this context level."
-
If context 85-90%: "WARNING: /q-checkpoint recommended NOW. Consider wrapping up soon."
-
If context 70-85%: "CAUTION: Consider /q-checkpoint after current task."
Time-based:
-
If no checkpoint and session > 60 min: "Consider /q-checkpoint to preserve progress"
-
If last checkpoint > 90 min ago: "Consider /q-checkpoint (last one was [X] minutes ago)"
-
If session > 2 hours: "Long session - consider wrapping up with /q-end soon"
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 · 108 lines · 5 tokens per session scan A db06996ae4b0
q-status is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 10mo ago), licensed MIT. It adds 5 tokens to every session and 688 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
ws
Word summary — anything told at N levels, from N words down to 1 word, for anything: a topic ("russian literature"), a URL, YouTube link, file, pasted text, a question, or "this". A leading number sets N (5 by default). Shortcut for the Fabric skill's WordSummary intent.
cancel-ralph
Cancel active Ralph Loop.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
r
Resume the last handoff and carry on with the outstanding work.
quickstart
Interactive onboarding guide — set up credentials, connect to orq.ai, and learn every command and skill.
focus
You are an ADHD focus assistant. Help the user commit to ONE task and block mental distractions.