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/commerce-atoms/agents/releasegit clone --depth 1 https://github.com/commerce-atoms/agentsWhat 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.00022 | $0.01003 |
| Opus 5 | $0.00011 | $0.00502 |
| Sonnet 5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00100 |
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 yesterday.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release [patch|minor|major]
Doctrine reminder (
AGENTS.md §0sub-doctrine): the agent prepares and validates. CI deploys. This command tags and pushes; GitHub Actions deploys on tag detection. The agent never runsshopify hydrogen deploy.
Cut a versioned release from main. Bumps package.json#version, updates CHANGELOG.md, creates an annotated git tag, and pushes — letting CI take it from there.
Prerequisites
- On
mainbranch. - Working tree clean.
/deploy-checkpassed.CHANGELOG.mdhas an[Unreleased]section with the changes shipping in this release.
Workflow
1. Verify branch and cleanliness
test "$(git rev-parse --abbrev-ref HEAD)" = "main" || echo "FAIL: not on main"
test -z "$(git status --porcelain)" || echo "FAIL: uncommitted changes"
Abort on either failure.
2. Run /deploy-check
If skipped, run it now. Do not release without a clean pre-flight.
3. Decide the bump
If the operator passed patch / minor / major, use that.
Otherwise, infer from commits since the last tag using Conventional Commit prefixes:
feat!:or anyBREAKING CHANGE:footer → major.feat:→ minor.fix:/chore:/docs:/refactor:→ patch.
Surface the inferred bump to the operator and pause for confirmation:
Last tag: v0.4.2
Inferred bump: minor
Next version: v0.5.0
Confirm? (y/n)
4. Update package.json and CHANGELOG.md
- Bump
package.json#versionto the new SemVer. - In
CHANGELOG.md, rename the[Unreleased]heading to[<new-version>] — <YYYY-MM-DD>and add a fresh empty[Unreleased]section above it. - Stage both files.
5. Commit, tag, push
git add package.json CHANGELOG.md
git commit -m "chore(release): v<new-version>"
git tag -a "v<new-version>" -m "Release v<new-version>"
git push origin main
git push origin "v<new-version>"
6. Tell the operator what's happening
Released v<new-version>.
GitHub Actions is now deploying (CI: .github/workflows/deploy.yml).
Watch the run: gh run watch
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.
- yesterday First seen · 110 lines · 22 tokens per session scan A 2d4f0bd14ee2
release is a command published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,003 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
fastapi_stripe
A Stripe Checkout implementation takes four steps.
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
resolve-conflicts
Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.
brownfield-map
Run a complete brownfield analysis on the codebase and generate MASTER.md, summaries, risk scores, and all derived analytics.
react-router-client-loader
Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.