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-commit)<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-commit"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/contacttam/q-command-system/q-commit"><img src="https://agentmods.dev/badge/commands/contacttam/q-command-system/q-commit.svg" alt="Reviewed on agentmods" width="80" 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.00005 | $0.00316 |
| Opus 5.5 | $0.00002 | $0.00126 |
| Sonnet 5.5 | $0.00001 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
q-commit 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 2mo 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
Commit Changes
Purpose: Stage and commit all changes to local git.
Step 1: Save All Changes
Ensure all file changes are saved.
Step 2: Check Status
git status
Show what will be committed. If nothing to commit, report and stop.
Step 3: Stage Changes
git add .
Step 4: Create Commit
Commit with descriptive message:
git commit -m "Brief summary of changes
- Point 1: description
- Point 2: description
- Point 3: description
Co-Authored-By: Claude <[email protected]>"
Message guidelines:
- First line: Brief summary (50 chars or less)
- Blank line
- Bullet points of specific changes
- Co-author attribution
Step 5: Verify
git status
Should show: "nothing to commit, working tree clean"
Step 6: Report
Committed: [hash]
[Full commit message]
Working tree clean. Ready to push when you're ready: git push
Important: This command NEVER pushes to remote. User controls when to push.
When to use:
- Mid-session to save work in progress
- As part of /q-end workflow
- After completing a logical unit of work
- Before switching to different task
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.
- 2mo ago First seen · 75 lines · 5 tokens per session scan A f9399e7491be
q-commit is a command published in the GitHub repository contactTAM/q-command-system (5 stars, last pushed 10mo ago), licensed MIT. It adds 5 tokens to every session and 316 once invoked, about $0.0000 per session on Opus 5.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
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.