Borrowing it
Nothing to install: this file belongs to danikf/tik4net. 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/danikf/tik4net/master/.claude/skills/pre-release-check/SKILL.mdgit clone --depth 1 https://github.com/danikf/tik4netWrote 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/danikf/tik4net/pre-release-check)<a href="https://agentmods.dev/skills/danikf/tik4net/pre-release-check"><img src="https://agentmods.dev/badge/skills/danikf/tik4net/pre-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/danikf/tik4net/pre-release-check"><img src="https://agentmods.dev/badge/skills/danikf/tik4net/pre-release-check.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.00145 | $0.05740 |
| Opus 5.5 | $0.00058 | $0.02296 |
| Sonnet 5.5 | $0.00029 | $0.01148 |
| Haiku 4.5 | $0.00015 | $0.00574 |
Grade A, and why
pre-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 yesterday.
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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-release check
A release is the moment the library stops being ours and starts being somebody's dependency. This skill is the list of things worth knowing before that, split by whether a machine can decide them.
Two rules govern everything below.
A check that could not have failed has measured nothing. Before believing a green result, ask what outcome would have been red. This is not paranoia — it is how a whole class of green runs turn out to be runs that never executed. See the traps section; each entry there is a real one from this repository.
Severity is about the user, not about the finding. A wrong answer the caller cannot detect outranks a crash, which outranks anything cosmetic. A library that silently returns different data on a Czech machine is worse than one that throws.
The two lanes
Keep them apart. Mixing them is how a release checklist becomes a wall nobody reads.
| Gates | Reviews | |
|---|---|---|
| Decided by | a command, deterministically | judgement |
| Failure means | do not tag | write it down, then decide |
| Where they live | CI where possible, this skill otherwise | this skill, usually delegated to an agent |
Run the gates first — they are cheap and they can invalidate the reviews.
Part 1 — Gates
1.0 Is the version ready?
A version is ready when its key features are done and no bug is open — measured by exactly that, not by how long it has been in development or how much else landed.
- Key features: the version's list under What's new in
README.md(mirrored on the wiki'sHome). Every bullet ships and works; none still says (planned). A feature that will not make it is moved to the next version's list, not left planned in a tagged one. - No open bug: nothing open in the version's todo (the maintainer's local release notes — ask for them), and no open GitHub issue labelled as a bug against it. A known defect is fixed or explicitly moved out with the maintainer's decision, never shipped unmentioned.
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.
- yesterday Changed b92f6fd9160e
- 19d ago Changed · +47 lines 51c85f8fa1e6
- 1mo ago Changed · +17 lines 3ef8eac84548
- 1mo ago Changed · +6 lines f350e8e72aca
- 2mo ago First seen · 344 lines · 145 tokens per session scan A 067a52a9cea5
pre-release-check is a skill published in the GitHub repository danikf/tik4net (198 stars, last pushed yesterday), licensed Apache-2.0. It adds 145 tokens to every session and 5,740 once invoked, about $0.0006 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.
create-release
Create a versioned GitHub release with changelog.
bump-version
Bump the SSW.VerticalSliceArchitecture.Template NuGet package version to cut a new release. Use when the user says "bump the version", "cut a release", "release a new version", "publish a new package version", or similar for this template repo. Edits the version in VerticalSliceArchitecture.nuspec — which is what…
safe-github-push
A workflow for safely pushing Git repositories that contain large assets or binary files to GitHub. It checks repository changes and file sizes before planning commits and pushes.
maf-release-watcher
Detects new MAF releases and keeps the registry, matrix and guides current. Pipeline: (1) the watcher diffs every tracked package surface and opens a scaffold PR on a per-version branch, (2) the maf-registry-fill agentic workflow fills the TODOs inside Actions, (3) required PR gates decide; releases without breaking…
release
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.