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 agentmods add skills/danikf/tik4net/pre-release-checknpx skills add danikf/tik4net --skill pre-release-checkgit 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.svg" alt="Measured on agentmods" 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.00145 | $0.04642 |
| Opus 5 | $0.00072 | $0.02321 |
| Sonnet 5 | $0.00029 | $0.00928 |
| Haiku 4.5 | $0.00015 | $0.00464 |
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 6d 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 — 344 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.1 Build, tests, packages
dotnet build tik4net.sln --configuration Release -warnaserror
dotnet test tik4net.unittests/tik4net.unittests.csproj --configuration Release
Then the integration suite per the mikrotik-tests skill: a full pass on the binary API, plus the smoke
subset on the other transports. For a release, run the full 11-transport matrix — this is one of the
two occasions that justifies it.
Packaging is validated by CI (.github/workflows/build.yml packs all three and asserts both TFMs exist),
but before a tag also unzip the .nupkg and check by eye:
lib/netstandard2.0/andlib/net8.0/each hold bothtik4net.dllandtik4net.objects.dll, and the.xmldoc file beside each..nuspec<dependencies>names no internal id.tik4net.core.internalappearing there means aProjectReferencelost itsPrivateAssets="all", and the package will fail to restore for everyone.LICENSEandREADME.mdare inside.
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.
- 6d 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 (197 stars, last pushed yesterday), licensed Apache-2.0. It adds 145 tokens to every session and 4,642 once invoked, about $0.0007 per session on Opus 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.
azsdk-common-prepare-release-plan
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. UTILITY SKILL. USE FOR: "create release plan", "get release plan", "update release plan", "update API spec in release plan", "update SDK details in release plan", "abandon release plan", "link SDK PR to plan", "namespace…
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
azsdk-common-sdk-release
Check release readiness and trigger the release pipeline for Azure SDK packages. UTILITY SKILL. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES…
release-readiness
Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs or Loop-page drafts from the resulting evidence. Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions…
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.