Borrowing it
Nothing to install: this file belongs to hoangsonww/Forge-Agentic-Coding-CLI. 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/hoangsonww/Forge-Agentic-Coding-CLI/master/.agents/skills/release-check/SKILL.mdgit clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWrote 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/skills/hoangsonww/forge-agentic-coding-cli/release-check)<a href="https://agentmods.dev/skills/hoangsonww/forge-agentic-coding-cli/release-check"><img src="https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/release-check/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/skills/hoangsonww/forge-agentic-coding-cli/release-check"><img src="https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/release-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 37 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
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.00030 | $0.00353 |
| Opus 5.5 | $0.00012 | $0.00141 |
| Sonnet 5.5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
release-check 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 2mo 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
A bad release is worse than a late release. Do each step manually.
1. Clean tree
git status # must be clean
git fetch origin
git log --oneline origin/master..HEAD # what's going out
2. Version + changelog
package.jsonversion bumped per semver.CHANGELOG.mdhas a section for this version (Added / Changed / Fixed / Security), referencing issues/PRs.
3. Run the verify skill
All 249+ tests pass; format, lint, typecheck, build all clean.
4. Docs
- README "At a glance" counts match reality.
docs/ARCHITECTURE.mdreflects hot-path changes.docs/SETUP.md/docs/INSTALL.mdreflect new env vars or deps.- If any counts changed:
bash scripts/metrics.sh.
5. Docker
docker build -f docker/Dockerfile -t forge:dev .
docker run --rm forge:dev doctor --no-banner
6. Smoke test
npm run build
./bin/forge.js doctor
./bin/forge.js --version
7. Tag
Only after every step above passes. The tag triggers a 6-stage release workflow — do not push one you haven't verified.
git tag v<x.y.z>
git push origin v<x.y.z>
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.
- 2mo ago First seen · 57 lines · 30 tokens per session scan A 12cf36c43c4d
release-check is a skill published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (26 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 353 once invoked, about $0.0001 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.
release-check compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| release-checkhoangsonww/Forge-Agentic-Coding-CLI | Skill | 26 | 1mo ago | MIT | A | 30 | Claude Code, Codex |
| git-commit-helperalirezarezvani/claude-code-tresor | Skill | 782 | 4mo ago | MIT | A | 55 | Claude Code |
| mergendisisnd/msg | Skill | 6 | 19d ago | MIT | C | 126 | Claude Code |
| agent-release-managerruvnet/ruflo | Skill | 81k | yesterday | MIT | A | 16 | Claude Code |
| agent-release-swarmruvnet/ruflo | Skill | 81k | yesterday | MIT | A | 19 | Claude Code |
| agent-github-modesruvnet/ruflo | Skill | 81k | yesterday | MIT | A | 21 | Claude Code |
| github-automationruvnet/ruflo | Skill | 81k | yesterday | MIT | A | 61 | Claude Code |