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 instructions/contacttam/q-command-system/claude-mdgit 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/instructions/contacttam/q-command-system/claude-md)<a href="https://agentmods.dev/instructions/contacttam/q-command-system/claude-md"><img src="https://agentmods.dev/badge/instructions/contacttam/q-command-system/claude-md.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.02011 | $0.02011 |
| Opus 5 | $0.01006 | $0.01006 |
| Sonnet 5 | $0.00402 | $0.00402 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
q-command-system CLAUDE.md 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 5d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Q-Command System Repository
A Robust Co-Pilot System for Claude Code
Version: 2.1.2 Author: Gabriel Rymberg Repository: github.com/contactTAM/q-command-system License: MIT
What is This Repository?
This repository IS the Q-Command System - the source code, documentation, templates, and examples for the comprehensive co-pilot framework that structures Claude Code sessions.
Meta Usage: This repository uses its own Q-Command System to manage its own development. We practice what we preach!
Project Purpose
The Q-Command System transforms Claude Code from a simple AI assistant into a reliable development co-pilot with:
- Structured session management (
/q-begin,/q-end,/q-checkpoint) - Automatic documentation (transcripts, session notes)
- Context awareness and protection
- Multi-user support without file collisions
- Git workflow integration
- Explicit verification and error handling
This repository contains:
/docs/- Comprehensive documentation/templates/.claude/commands/- Slash command definitions (15 files)/templates/.q-system/- Q-System folder template (docs, config, session folders)/templates/CLAUDE.md- Template for your CLAUDE.md
Current Status
Version: 2.1.2 (Released 2025-12-03)
Latest Updates:
- Q Marketplace footer in session commands (q-begin, q-end, q-checkpoint)
- SHARE.md template for viral distribution
- First-session welcome template in CLAUDE.md
- 3 Quick Start Guides (Q, Git, Claude Code Tips)
- Standard headers/footers across all documentation
Repository State: Stable, ready for public use
Team
Primary Maintainer:
- Gabriel Rymberg - Creator and lead developer
Contributors: Open to community contributions
Usage: This repository uses Q-commands for all development work
Repository Structure
Q-command-system/
├── getting-started.md <- Start here
├── README.md <- Overview + install instructions
├── CHANGELOG.md <- Version history
│
├── templates/
│ ├── .claude/commands/ <- Slash command definitions (15 files)
│ ├── .q-system/ <- Q-System folder template
│ │ ├── docs/ <- Documentation (copied during install)
│ │ ├── config.md <- User preferences template
│ │ └── README.md <- Folder explanation
│ └── CLAUDE.md <- Template for your CLAUDE.md
│
├── docs/ <- Source documentation
│ ├── install/
│ ├── features.md
│ ├── workflow.md
│ └── context-management.md
│
└── .q-system/ <- Session files for THIS repo
├── transcripts/
├── session-notes/
├── checkpoints/
└── config.md
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.
- 5d ago First seen · 260 lines · 2,011 tokens per session scan A df7c16fe43eb
q-command-system CLAUDE.md is an instructions file published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 8mo ago), licensed MIT. It adds 2,011 tokens to every session, about $0.0101 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 instructions, from other repositories
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).