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/florianbruniaux/ctxharness/commitgit clone --depth 1 https://github.com/FlorianBruniaux/ctxharnessWhat 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.00000 | $0.00281 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
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 2d 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
Conventional Commit
Create a git commit following conventional commits format for ctxharness.
Steps
- Run
git statusandgit diff --stagedto see what's staged - If nothing staged, run
git add -pguidance or ask user what to stage - Draft commit message:
- Format:
type(scope): short description - Types:
feat,fix,docs,test,refactor,chore,build - Scopes:
core,cli,extractors,scanners,runner,reporter,config,gha,hooks
- Format:
- Commit with:
git commit -m "type(scope): description"
Examples
feat(extractors): add prismaEnum extractor for schema drift detection
fix(scanners): handle empty YAML field gracefully
test(runner): add integration test for no-mention status
docs(readme): add v0.2 stack-aware extractor table
chore(deps): bump zod to 3.24.5
build(gha): add node-version matrix to CI workflow
Rules
- Subject line max 72 chars, no period at end
- Body optional: explain WHY not WHAT
- Never
--no-verify - Never amend published commits
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.
- 2d ago First seen · 32 lines · 0 tokens per session scan A ff54ce044d76
commit is a command published in the GitHub repository FlorianBruniaux/ctxharness (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 281 tokens. 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-30.
Other commands, from other repositories
commit
Command "commit" from liam-hq/liam, covering examples, gitmoji reference, frequently used, testing & quality and critical changes.
save
Command "save" from anton-abyzov/specweave, covering save changes across repositories, usage, interactive (prompts for commit message), dry run (show what would happen, don't execute) and save specific repos only (umbrella mode).
mach12:push
Commit, push, and post a progress comment using session context or branch detection.
dream-apply
Walk a dream proposal artifact, review each item, apply accepted ones, commit.
push
Commit, push, and post a progress comment using session context or branch detection.
conclude
Use at session end to save project learnings and produce a commit message.