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-savegit 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-save)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-save"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-save.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.00005 | $0.01074 |
| Opus 5 | $0.00003 | $0.00537 |
| Sonnet 5 | $0.00001 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
q-save 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Save
Purpose: Lightweight session wrap-up when time or context is limited.
USE THIS WHEN: Context is critical (>90%) or you need to exit immediately.
MANDATORY PRE-FLIGHT CHECKLIST
STOP. Before proceeding, confirm:
- 1. I will generate and USE the timestamp
- 2. I will create the transcript file (even if brief)
- 3. I will commit changes
- 4. I will VERIFY both file and commit
Step 1: Generate Timestamp
EXECUTE this exact command:
TIMESTAMP=$(date +"%Y-%m-%d-%H%M") && echo "TIMESTAMP: $TIMESTAMP"
- Command executed
- Timestamp captured: ____________________
- Format verified: YYYY-MM-DD-HHMM
STORE this timestamp. Use it for ALL operations.
Step 2: Determine Participant Name
- Name known from session: ____________________
- OR use: "Unknown"
Step 3: Create Basic Transcript
3.1 Create Directory
mkdir -p .q-system/transcripts
3.2 Create File
Filename: .q-system/transcripts/${TIMESTAMP}-[Name].md
MANDATORY content (keep it brief but complete):
# Session: [TIMESTAMP]-[Name]
**Type:** Quick save (abbreviated due to context constraints)
---
## Key Accomplishments
- [Accomplishment 1]
- [Accomplishment 2]
- [List ALL major work items]
---
## Files Changed
**Created:**
- [file1]
**Modified:**
- [file1]
---
## Status at Exit
[Current state - what's done, what's pending]
---
## Note
Quick save used due to: [context limit / time constraint / emergency exit]
Full session notes not created. Review checkpoints if available.
- File created
- All accomplishments listed (even if brief)
- Files changed listed
3.3 VERIFY File
ls -la .q-system/transcripts/${TIMESTAMP}* && wc -l .q-system/transcripts/${TIMESTAMP}*
- File exists
- File has content (>15 lines minimum)
VERIFICATION GATE 1:
Transcript created: .q-system/transcripts/[filename]
- Lines: [N]
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 · 223 lines · 5 tokens per session scan A af04a0771a2c
q-save is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 8mo ago), licensed MIT. It adds 5 tokens to every session and 1,074 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.