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-prompts)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-prompts"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-prompts.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.1 | $0.00006 | $0.00426 |
| Opus 5 | $0.00003 | $0.00213 |
| Sonnet 5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
q-prompts 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 8d 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
Save Session Prompts
Purpose: Extract and save all user prompts/instructions from this session for future reference and reuse.
Step 1: Generate Timestamp
TIMESTAMP=$(date +"%Y-%m-%d-%H%M")
Step 2: Create Directory
mkdir -p .q-system/prompts
Step 3: Determine Participant Name
Use known name or ask user.
Step 4: Extract Prompts
Review the entire conversation and extract:
- Every user message/instruction
- In chronological order
- Exactly as written (or slightly cleaned up for clarity)
Step 5: Create Prompts File
Create .q-system/prompts/${TIMESTAMP}-[Name].md:
# Session Prompts: [TIMESTAMP]
**Date:** [YYYY-MM-DD]
**Participant:** [Name]
---
## Prompts (Chronological)
1. [First user prompt]
2. [Second user prompt]
3. [Third user prompt]
[Continue for all prompts...]
---
## Useful Prompts to Reuse
### [Category: e.g., "Code Review"]
- "[Prompt that worked well]"
### [Category: e.g., "Documentation"]
- "[Prompt that worked well]"
---
**Total prompts:** [N]
Step 6: Verify and Report
Prompts saved: .q-system/prompts/[filename]
Total prompts captured: [N]
Highlighted [M] prompts as particularly useful for reuse.
Tip: Review this file to find prompts worth reusing in future sessions.
Why save prompts:
- Find effective prompts to reuse
- Track how you interact with Claude
- Build a personal prompt library
- Learn what instructions work well
When to use:
- End of productive session
- After discovering effective prompts
- When you want to remember how you asked for something
- Building a prompt library
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.
- 8d ago First seen · 94 lines · 6 tokens per session scan A 1190346f6abc
q-prompts is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 426 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.
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.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.