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 skills add ANcpLua/ancplua-claude-plugins --skill releasegit clone --depth 1 https://github.com/ANcpLua/ancplua-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/skills/ancplua/ancplua-claude-plugins/release)<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/release"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-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/skills/ancplua/ancplua-claude-plugins/release"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-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.00070 | $0.00601 |
| Opus 5.5 | $0.00028 | $0.00240 |
| Sonnet 5.5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
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 16d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
description: "Release-gate workflow with strict CI and publishing discipline. Inspects the repository's release workflow, verifies versioning and CI state, and refuses to publish when checks are red or unknown. Blocks fo How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nihil Release Gate
Activate Release Mode. Follow the repository's release workflow exactly. A
PreToolUse hook permits release-like commands but still blocks obviously destructive
ones (force-push, hard reset, rm -rf). It does not know your repo's workflow — you
do; respect it.
Critical instructions
- Inspect before acting. Read the repository's actual release workflow before
running anything: CI config (
.github/workflows/*), version source (*.csproj,Directory.Build.props,Version.props,package.json,pyproject.toml), tag conventions, and any documented release flow. Do not assume. - CI is the gate. A green CI run may publish. A red or unknown CI run must not publish. If you cannot verify CI state, treat it as unknown and block.
- Version/tag agreement. Commit, push, bump versions, and create tags only when
the task is complete, the repository expects those actions, and required checks
have passed. Ensure
plugin.json/ package version and any enclosing marketplace entry agree before tagging.
NuGet
When NuGet publishing is involved, use trusted publishing as the reference — short-lived OIDC tokens from CI, no long-lived API keys committed or printed: https://learn.microsoft.com/en-gb/nuget/nuget-org/trusted-publishing. Never print or commit a real API key or token.
Use nihil:release-gatekeeper (read-only, via the Task tool) to audit CI, version,
tag, and publishing safety before you decide.
Output
Produce exactly this structure (the Stop hook blocks once if a readiness / blockers section is missing):
# Nihil Release Gate
## Release Readiness
<is the work complete and does the repo expect a release now?>
## Required Checks
<each required check and its observed state — green / red / unknown>
## Version / Tag Decision
<the exact version and tag, and confirmation that all version sources agree>
## Publishing Decision
Publish / Do not publish — with the CI evidence that justifies it.
## Blockers
<anything red or unknown that prevents release, or "None.">
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.
- 16d ago First seen · 67 lines · 70 tokens per session scan C f92af13f10ce
release is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 5d ago), licensed MIT. It adds 70 tokens to every session and 601 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ct-release-orchestrator
Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo release open, then PR + GHA tag workflow, then cleo release reconcile. The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.