Borrowing it
Nothing to install: this file belongs to swoopeagle/standardgraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/swoopeagle/standardgraph/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/swoopeagle/standardgraphWrote 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/swoopeagle/standardgraph/release)<a href="https://agentmods.dev/commands/swoopeagle/standardgraph/release"><img src="https://agentmods.dev/badge/commands/swoopeagle/standardgraph/release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/swoopeagle/standardgraph/release"><img src="https://agentmods.dev/badge/commands/swoopeagle/standardgraph/release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00425 |
| Opus 5.5 | $0.00000 | $0.00170 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade C, and why
release scanned grade C with 1 finding 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 1mo 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
`--token` inline, which has a quoting bug that silently sends an empty bearer token): What it actually says
Release a new version of StandardGraph to PyPI (and optionally HuggingFace).
Steps to follow in order:
- Read the current version from
packages/common-core/pyproject.toml - Ask the user what the new version should be (patch/minor/major bump, or explicit string)
- Update the version in
packages/common-core/pyproject.toml - Run
cd /Users/ianwang/projects/standardgraph/packages/common-core && uv build— confirm it succeeds and note the output dist files - Ask the user for their PyPI token (remind them to rotate it immediately after use)
- Run:
uvx twine upload --username __token__ /Users/ianwang/projects/standardgraph/dist/standardgraph-{VERSION}*with the token as TWINE_PASSWORD env var - Commit the version bump:
git add packages/common-core/pyproject.toml && git commit -m "Bump version to {VERSION}" - Push to GitHub:
git push origin main - Ask: "Did the DB change since last release? If yes, upload to HuggingFace."
- If yes: ask for HuggingFace token, then run (note:
huggingface-cliis deprecated and no longer works — use the modernhfCLI instead, and export the token rather than passing--tokeninline, which has a quoting bug that silently sends an empty bearer token):
Remind to rotate token.export HF_TOKEN='<token>' uvx --from huggingface_hub hf upload swoopeagle/standardgraph ~/.standardgraph/common_core.db common_core.db --repo-type dataset - Run
/statsto verify docs numbers match the live DB. - Report: PyPI URL, GitHub commit, and whether HF was updated.
Important: ALWAYS remind the user to rotate any tokens shared in chat. Tokens should never persist in shell history — pass them via env vars, not positional args.
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.
- 1mo ago First seen · 26 lines · 0 tokens per session scan C d6d8f366d4ea
release is a command published in the GitHub repository swoopeagle/standardgraph (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 425 tokens. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.