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 fpindej/netrock --skill create-releasegit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/create-release)<a href="https://agentmods.dev/skills/fpindej/netrock/create-release"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/create-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/fpindej/netrock/create-release"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/create-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00681 |
| Opus 5.5 | $0.00004 | $0.00272 |
| Sonnet 5.5 | $0.00002 | $0.00136 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
create-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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creates a GitHub release with auto-generated release notes.
Hard rules
- Only release from master. If not on master, switch first.
- No Co-Authored-By lines in commits.
- Tag signing follows the developer's git config (
tag.gpgSign) - never pass-s/-Sexplicitly; fresh clones may have no signing key. - Releases use semantic versioning (vMAJOR.MINOR.PATCH).
Steps
-
Ensure you are on
masterand up to date:git checkout master && git pull -
Determine the version:
- If the user provided a version (e.g.,
v1.2.3), use it - If the user provided a bump type (
major,minor,patch), calculate from the latest tag:git tag --list 'v*' --sort=-v:refname | head -1 - If no argument and no tags exist, ask the user what version to use
- If no argument but tags exist, default to
patchbump
- If the user provided a version (e.g.,
-
Check what changed since the last release:
# If previous tag exists: git log <previous-tag>..HEAD --oneline # If first release: git log --oneline -50 -
Generate release notes by categorizing merged PRs and commits since the last tag. Group changes into these categories (omit empty categories):
- New Features -
feat:commits and feature PRs - Security -
security:or security-related changes - Bug Fixes -
fix:commits - Improvements -
refactor:,perf:commits - Documentation -
docs:commits - Infrastructure -
chore:,ci:,build:commits
Format each entry as:
- Description (#PR)where possible.Add a brief intro paragraph summarizing the release highlights before the categories.
- New Features -
-
Create the tag and release:
git tag -a <version> -m "Release <version>" git push origin <version> gh release create <version> --title "<version>" --notes "<release-notes>" -
Report the release URL.
Version Bumping Reference
Given vMAJOR.MINOR.PATCH:
major- breaking changes or major milestones (v1.0.0 -> v2.0.0)minor- new features, no breaking changes (v1.0.0 -> v1.1.0)patch- bug fixes, docs, refactors (v1.0.0 -> v1.0.1)
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 · 68 lines · 10 tokens per session scan A 597842b2e79d
create-release is a skill published in the GitHub repository fpindej/netrock (234 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 681 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 skills, from other repositories
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.