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-checkpointgit 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-checkpoint)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-checkpoint"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-checkpoint.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.01115 |
| Opus 5 | $0.00003 | $0.00558 |
| Sonnet 5 | $0.00001 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
q-checkpoint 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 4d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpoint
Purpose: Save progress mid-session as insurance against auto-compact or crashes.
MANDATORY PRE-FLIGHT CHECKLIST
STOP. Before proceeding, confirm:
- 1. I will generate and USE the timestamp
- 2. I will document ALL work done since session start or last checkpoint
- 3. I will VERIFY the file was created
Step 1: Generate Timestamp
EXECUTE this exact command:
CHECKPOINT_TIME=$(date +"%Y-%m-%d-%H%M") && echo "CHECKPOINT_TIME: $CHECKPOINT_TIME"
- Command executed
- Timestamp captured: ____________________
- Format verified: YYYY-MM-DD-HHMM
STORE this timestamp. Use it for the checkpoint filename.
Step 2: Create Checkpoint Directory
mkdir -p .q-system/checkpoints
- Directory exists or created
Step 3: Determine Participant Name
- Name known from session: ____________________
- OR ask user: "What name should I use for the checkpoint file?"
Participant name: ____________________
Step 4: Gather All Work Since Last Save Point
MANDATORY: Review and document ALL of the following:
4.1 Accomplishments
- List every task completed
- List every file created
- List every file modified
- List every bug fixed
4.2 Decisions Made
- List every decision made
- Note rationale for each
4.3 Current State
- What are you working on RIGHT NOW?
- What is partially complete?
- What remains to be done?
VERIFICATION GATE 1:
Work to document:
- Accomplishments: [N] items
- Files changed: [N] files
- Decisions: [N] decisions
- Current task: [description]
Step 5: Create Checkpoint File
Filename: .q-system/checkpoints/${CHECKPOINT_TIME}-[Name].md
MANDATORY content structure:
# Checkpoint: [CHECKPOINT_TIME]-[Name]
**Session started:** [time if known]
**Checkpoint time:** [CHECKPOINT_TIME]
**Participant:** [Name]
---
## Accomplishments So Far
- [Accomplishment 1]
- [Accomplishment 2]
- [Continue for ALL accomplishments]
---
## Files Changed
**Created:**
- [file1]
- [file2]
**Modified:**
- [file1]
- [file2]
---
## Key Decisions
| Decision | Rationale |
|----------|-----------|
| [decision] | [why] |
---
## Current Status
**Working on:** [what you're doing right now]
**Partially complete:** [what's in progress]
---
## Next Steps
- [ ] [Next task 1]
- [ ] [Next task 2]
- [ ] [Continue for remaining 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.
- 4d ago First seen · 234 lines · 5 tokens per session scan A 5b734a33ace2
q-checkpoint 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,115 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.
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.
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.