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-dumpgit 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-dump)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-dump"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-dump.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.00004 | $0.00476 |
| Opus 5 | $0.00002 | $0.00238 |
| Sonnet 5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
q-dump 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
Dump Session Transcript
Purpose: Create a session transcript without the full /q-end workflow.
Step 1: Check for Continued Sessions
- Look for: "This session is being continued from a previous conversation"
- If present, the conversation summary contains work before auto-compact
- You MUST document the ENTIRE session (summary + current context)
Step 2: Determine Session Start Time
- Regular session: Use current session start time
- Continued session: Use ORIGINAL session start time from summary
Step 3: Generate Timestamp
TIMESTAMP=$(date +"%Y-%m-%d-%H%M")
Step 4: Create Transcript Directory
mkdir -p .q-system/transcripts
Step 5: Determine Participant Name
Use known name or ask user.
Step 6: Create Transcript File
Create .q-system/transcripts/${TIMESTAMP}-[Name].md:
# Session Transcript: [TIMESTAMP]
**Date:** [YYYY-MM-DD]
**Participant:** [Name]
**Duration:** [X hours Y minutes]
**Type:** [Regular / Continued from auto-compact]
---
## Session Flow
### [Time] - [Topic/Task]
[Description of what was discussed/done]
### [Time] - [Topic/Task]
[Description of what was discussed/done]
[Continue chronologically...]
---
## Summary
### Accomplishments
- [Bullet list]
### Files Changed
- Created: [list]
- Modified: [list]
### Key Decisions
- [Decision]: [Rationale]
### Metrics
- Duration: [X hours Y minutes]
- Files changed: [N]
- Commits: [N]
Step 7: Verify and Report
VERIFY: File exists and has substantial content (>50 lines for real sessions)
Transcript created: .q-system/transcripts/[filename]
- Duration: [X hours Y minutes]
- [N] lines documented
Difference from /q-end:
- /q-dump: Only creates transcript
- /q-end: Creates transcript + session notes + commits
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 · 98 lines · 4 tokens per session scan A 63e49d052d6f
q-dump is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 8mo ago), licensed MIT. It adds 4 tokens to every session and 476 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.