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/clawforgeai/clawforge/releasegit clone --depth 1 https://github.com/ClawForgeAI/clawforgeWrote 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/clawforgeai/clawforge/release)<a href="https://agentmods.dev/commands/clawforgeai/clawforge/release"><img src="https://agentmods.dev/badge/commands/clawforgeai/clawforge/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.00356 |
| Opus 5 | $0.00000 | $0.00178 |
| Sonnet 5 | $0.00000 | $0.00071 |
| 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 today.
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 Workflow
Guide through the changeset-based release process for the @clawforgeai/clawforge plugin.
Note: Only the plugin/ package is published to npm. Server and admin are excluded (see .changeset/config.json).
Instructions
Determine the release stage from: $ARGUMENTS
If no argument given, ask the user which step they need:
Step 1: Create changeset (create)
- Ask what changed and whether it's a patch, minor, or major bump
- Run
pnpm changeset - The user selects
@clawforgeai/clawforgeand bump type interactively - Review the generated
.changeset/*.mdfile - Commit the changeset file
Step 2: Check pending changesets (check)
- List files in
.changeset/directory (exclude config.json and README.md) - Read each changeset file and summarize pending version bumps
- Report current plugin version from
plugin/package.json
Step 3: Version bump (version)
- Run
pnpm version-packagesto apply changesets - Review changes to
plugin/package.jsonversion andCHANGELOG.md - Commit the version bump
Step 4: Verify before publish (verify)
- Run
pnpm --filter @clawforgeai/clawforge build - Run
pnpm --filter @clawforgeai/clawforge test - Report build and test results
Note: Actual npm publishing happens via the GitHub Actions release workflow (.github/workflows/release.yml) when the "Version Packages" PR is merged to main.
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.
- today First seen · 40 lines · 0 tokens per session scan A 33779a375b59
release is a command published in the GitHub repository ClawForgeAI/clawforge (17 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 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-09-04.
Other commands, from other repositories
spec
Manage specifications in our development process.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
status
Run a full MCPWorks platform status check using the admin function suite via mcpmcpworks-runexecute.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.