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/releasegit clone --depth 1 https://github.com/FlorianBruniaux/ctxharnessWrote 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/florianbruniaux/ctxharness/release)<a href="https://agentmods.dev/commands/florianbruniaux/ctxharness/release"><img src="https://agentmods.dev/badge/commands/florianbruniaux/ctxharness/release.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.00000 | $0.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
release 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.
What it actually says
Release ctxharness
Bump version, update CHANGELOG, build, test, tag, publish.
Steps
- Determine bump type from argument:
patch|minor|major - Read current version from
packages/core/package.json - Compute new version (semver bump)
- Update version in:
packages/core/package.jsonpackages/cli/package.jsonpackage.json(root, if it has version)
- Update CHANGELOG.md: rename
[Unreleased]to[vX.Y.Z] - YYYY-MM-DD, add new empty[Unreleased]section - Build:
pnpm build - Test:
pnpm test - Commit:
git commit -am "release: vX.Y.Z" - Tag:
git tag vX.Y.Z - Push:
git push && git push --tags - Publish:
pnpm -r publish --no-git-checks #confirmed
Usage
/release patch # 0.1.0 → 0.1.1
/release minor # 0.1.0 → 0.2.0
/release major # 0.1.0 → 1.0.0
Pre-flight checklist
-
pnpm testpasses (31 tests) -
CHANGELOG.md [Unreleased]has content - No uncommitted changes after release commit
- Both
packages/*/package.jsonhave matching versions
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 · 36 lines · 0 tokens per session scan A ce221d0f61c9
release 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 363 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
release
Release a new version: bump version, update changelog, tag, push, and create a GitHub release.
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
mach12:pr-create
Create a pull request for the current branch with structured description.
mach12:pr-merge
Merge a PR, delete the feature branch, and optionally create a release.
mach12:push
Commit, push, and post a progress comment using session context or branch detection.