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/alirezarezvani/claude-code-skill-factoryWrote 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/alirezarezvani/claude-code-skill-factory/run-release)<a href="https://agentmods.dev/commands/alirezarezvani/claude-code-skill-factory/run-release"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-code-skill-factory/run-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/alirezarezvani/claude-code-skill-factory/run-release"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-code-skill-factory/run-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.00011 | $0.00202 |
| Opus 5.5 | $0.00004 | $0.00081 |
| Sonnet 5.5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
run-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 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.
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
Pre-flight
- Complete the Release Checklist issue.
- Ensure
/reviewand/security-scanare green on the target branch.
Trigger Workflow
/run-release vX.Y.Z [target]
vX.Y.Z: Required semantic version tag (include thev).target: Optional branch/commit (defaults tomain).
Command
gh workflow run release-orchestrator.yml \
--ref ${target:-main} \
-f version=${version} \
-f target=${target:-main}
After Triggering
- Wait for the
Release Orchestratorworkflow to reach the environment approval step. - Approve the
releaseenvironment to publish the annotated tag and draft release. - Review and publish the draft release on GitHub.
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 · 31 lines · 11 tokens per session scan A bcf9b5f95557
run-release is a command published in the GitHub repository alirezarezvani/claude-code-skill-factory (892 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 202 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-08-30.
Other commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
versioning
Universal version file discovery and sync. Works with any project structure.
ship
Create a release PR to main with version bump and draft a GitHub release.
ship
Prepare the current branch for review and deployment.
README
Git workflow and quality assurance commands for the claude-skills repository.
cm
Stage working tree changes and create a Conventional Commit (no push).