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/sanmak/specops/releasegit clone --depth 1 https://github.com/sanmak/specopsWhat 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.01522 |
| Opus 5 | $0.00000 | $0.00761 |
| Sonnet 5 | $0.00000 | $0.00304 |
| Haiku 4.5 | $0.00000 | $0.00152 |
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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a versioned release: update CHANGELOG, bump version, validate, commit, push, and publish a GitHub Release.
Instructions
Follow these steps precisely. Do NOT add a Co-Authored-By line to the commit.
The version to release is provided via $ARGUMENTS. If $ARGUMENTS is empty or missing, ask the user "What version should this release be? (format: MAJOR.MINOR.PATCH)" and wait for their response before continuing.
Step 1: Validate version
Validate that the version matches semver format MAJOR.MINOR.PATCH (e.g., 1.2.0, 2.0.1). It must NOT have a v prefix -- strip it if present.
If invalid, inform the user and stop.
Step 2: Pre-flight checks
Run all of these checks. If any fail, report the issue and stop.
- Working tree is clean: Run
git status. If there are uncommitted changes, tell the user "Working tree is not clean. Run /commit first or stash changes before releasing." and stop. - On main branch: Run
git rev-parse --abbrev-ref HEAD. If not onmain, tell the user "Releases must be created from the main branch. Currently on<branch>." and stop. - No unpushed commits: Run
git log @{upstream}..HEAD --oneline. If there are unpushed commits, tell the user "There are unpushed commits. Run /push first." and stop. - GitHub CLI available: Run
gh --version. Ifghis not available, tell the user "GitHub CLI (gh) is required for creating releases. Install it with: brew install gh" and stop. - Tag does not exist: Run
git tag -l v<version>. If the tag already exists, tell the user "Tag v already exists. Choose a different version number." and stop.
Step 3: Gather changes since last release
- Find the last release tag:
git describe --tags --abbrev=0 2>/dev/null. If no tags exist, use the root commit. - List all commits since:
git log --oneline <last-tag>..HEAD - Read the full diffs for each commit to understand the actual changes:
git log -p <last-tag>..HEAD - Read the current
CHANGELOG.mdto check if there is existing content in the[Unreleased]section
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 · 136 lines · 0 tokens per session scan A 8cd782dc748d
release is a command published in the GitHub repository sanmak/specops (49 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,522 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
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
ijfw-metrics
Show IJFW token / cost / session metrics over a time window. Reads .ijfw/metrics/sessions.jsonl via the ijfwmetrics MCP tool.
analyze
在任务生成后，对 spec.md、plan.md 和 tasks.md 进行只读的一致性与质量分析。.
review-pr
Fetch a pull request diff, run code-reviewer analysis, translate findings to owner voice, and post a single batched inline GitHub review.
rea
Print REA session status — autonomy level, HALT state, policy profile, and recent audit entries.