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.
git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/release)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/release"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/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/joaquimscosta/arkhe-claude-plugins/release"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/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.00010 | $0.00282 |
| Opus 5.5 | $0.00004 | $0.00113 |
| Sonnet 5.5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 Command
Automate the full release process: validate CHANGELOG, update comparison links, commit, trigger GitHub Actions workflow, and monitor completion. Or scaffold release infrastructure for new projects.
Usage
/release <version> # Execute release (e.g., /release 1.6.0)
/release --setup # Scaffold release infrastructure
/release <version> --skip-monitor # Trigger without monitoring
Examples
/release 1.6.0 # Release version 1.6.0
/release v2.0.0 # Works with 'v' prefix too
/release --setup # Create release.sh, workflow, and helper scripts
Prerequisites
- GitHub CLI (
gh) installed and authenticated - CHANGELOG.md entry for the version (use
/changelogfirst) .github/workflows/release.ymlexists (use--setupto create)
Implementation
Invoke the Skill tool with skill name "git:releasing" and arguments: $ARGUMENTS
The skill handles version validation, CHANGELOG checks, comparison link management, commit/push, workflow triggering, and monitoring.
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 · 37 lines · 10 tokens per session scan A ac30690575c7
release is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 282 once invoked, about $0.0000 per session on Opus 5.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-10-16.
Other commands, from other repositories
ship
Complete PR workflow from commit to production with validation.
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
versioning
Universal version file discovery and sync. Works with any project structure.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
sync-ecosystem
Detect API changes, sync satellite repos, and publish releases.
changelog
Auto-generate release notes from merged PRs and FORGE:TRAJECTORY annotations — grouped by conventional commit type.