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-endgit 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-end)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-end"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-end.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.00006 | $0.01965 |
| Opus 5 | $0.00003 | $0.00983 |
| Sonnet 5 | $0.00001 | $0.00393 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
q-end 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End Session
Purpose: Complete session documentation and commit all changes.
MANDATORY PRE-FLIGHT CHECKLIST
STOP. Before proceeding, execute each item in order:
- 1. Read this ENTIRE command file top to bottom
- 2. Confirm you understand all 7 steps
- 3. You will NOT skip any step
- 4. You will VERIFY each step before proceeding to the next
DO NOT PROCEED until you have mentally confirmed all 4 items.
Step 1: MANDATORY - Gather ALL Prior Work
CRITICAL: This step is NON-NEGOTIABLE. Execute ALL sub-items.
1.1 Check for Continued Session
# Look for auto-compact continuation message in conversation
- Search conversation for: "This session is being continued from a previous conversation"
- If found: The conversation summary contains work BEFORE auto-compact - you MUST include this
1.2 MANDATORY: Read ALL Checkpoints From Today
ls -la .q-system/checkpoints/*$(date +%Y-%m-%d)* 2>/dev/null || echo "No checkpoints today"
EXECUTE the command above. Then:
- For EACH checkpoint file found: READ IT COMPLETELY
- Note accomplishments from each checkpoint
- Note files changed in each checkpoint
- Note decisions made in each checkpoint
If checkpoints exist and you did not read them: STOP and read them NOW.
1.3 Compile Complete Work List
- Work from conversation summary (if continued session)
- Work from ALL checkpoints (list each)
- Work from current conversation (after checkpoints)
VERIFICATION GATE 1:
I have gathered work from:
- [ ] Conversation summary: [YES/NO/N/A]
- [ ] Checkpoint files read: [list count or "none"]
- [ ] Current conversation: [YES]
TOTAL accomplishments to document: [NUMBER]
DO NOT PROCEED to Step 2 until you have completed this verification.
Step 2: 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
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 · 380 lines · 6 tokens per session scan A 64b3171c0fad
q-end 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 1,965 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
checkpoint
Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…
commit
智能创建 git 提交，分析代码变更并生成符合项目规范的提交信息.
git
Unified git operations - commits, pull requests, and issue management.
ship
Commit staged changes, push, and create PR.
changelog
Summarize staged git changes into a concise changelog/commit message.
commit
Create an atomic git commit with conventional message.