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/justinjdev/fight-club/releasegit clone --depth 1 https://github.com/justinjdev/fight-clubWrote 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/justinjdev/fight-club/release)<a href="https://agentmods.dev/commands/justinjdev/fight-club/release"><img src="https://agentmods.dev/badge/commands/justinjdev/fight-club/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.00025 | $0.00785 |
| Opus 5 | $0.00013 | $0.00392 |
| Sonnet 5 | $0.00005 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Automates the full release process for fellowship.
Step 1: Determine Version
Read the current version from .claude-plugin/plugin.json.
Analyze commits since the last tag (git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges) and suggest a version based on conventional commit types:
- feat: → minor bump
- fix: only → patch bump
- Breaking changes → minor bump (pre-1.0: major)
Present the suggestion and ask the user to confirm or override:
Current version: X.Y.Z
Commits since last tag: N
Suggested next version: X.Y.Z (reason)
Enter version to release (or confirm suggested):
Use AskUserQuestion with the suggested version as default and a free-text option.
Step 2: Audit Docs and Site
Before bumping anything, verify all documentation is current. Check each item and report status:
Changelog (site)
Read site/src/routes/changelog/+page.svelte. If there is an "Unreleased" section, it should be renamed to the new version. If there is no unreleased section and there are commits since the last changelog entry, flag it as needing an update.
Changelog (README)
Read README.md and check the ## Changelog section. If the latest entry doesn't cover the commits being released, flag it.
Skills page
Read site/src/routes/skills/+page.svelte. Cross-reference against plugin/skills/ and plugin/commands/ directories. Flag any skills or commands that exist but aren't documented.
Agents page
Read site/src/routes/agents/+page.svelte. Cross-reference against plugin/agents/ directory. Flag any agents that exist but aren't documented.
If any flags were raised, present them and ask the user whether to fix them now or proceed anyway. If fixing, make the updates before continuing.
Step 3: Bump Version
Update the version string in .claude-plugin/plugin.json.
If the site changelog has an "Unreleased" section, rename it to the new version with the standard format:
<section class="version" id="v{version-dashed}">
<h2 class="version-heading"><a href="{base}/changelog#v{version-dashed}">v{version}</a></h2>
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 · 102 lines · 25 tokens per session scan A dd11fe6b5c2d
release is a command published in the GitHub repository justinjdev/fight-club (1 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 785 once invoked, about $0.0001 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
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
release-check
Pre-release validation pipeline for a component.
release
Generate changelog, bump version, and create git tag.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
push
Push direction: ports local mechanism-script fixes back to the hub as a reviewed PR. Opposite of /update.