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/ozzyczech/dotfiles/npm-releasenpx skills add OzzyCzech/dotfiles --skill npm-releasegit clone --depth 1 https://github.com/OzzyCzech/dotfilesWrote 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/ozzyczech/dotfiles/npm-release)<a href="https://agentmods.dev/skills/ozzyczech/dotfiles/npm-release"><img src="https://agentmods.dev/badge/skills/ozzyczech/dotfiles/npm-release.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.00039 | $0.01926 |
| Opus 5 | $0.00019 | $0.00963 |
| Sonnet 5 | $0.00008 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
npm-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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 190 lines · 39 tokens per session scan A b17a7cd5fa8e
npm-release is a skill published in the GitHub repository OzzyCzech/dotfiles (136 stars, last pushed 12d ago), with no licence file. It adds 39 tokens to every session and 1,926 once invoked, about $0.0002 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
ship
Verify and publish by pushing, opening a PR, and watching CI; land mode merges then cleans branches. Triggers "ship it", "create PR", "/ship", "watch the PR", "babysit CI"; land mode "land it", "/ship land", "fix CI and merge".
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
github-workflow
Professional GitHub issue/PR workflow with gh CLI. Use when a best-practice use case needs issue → PR → Closes.
dot-release
Run dot release (or mise run release) to gate, bump, tag, and push a fmind/dot release that cd.yml publishes. Use when cutting a release of this repository.
sync-release
Owns release-pipeline conventions: sr.yaml schema, the sr CLI verbs (init/plan/prepare/ release) and urmzd/sr action, typed publishers (cargo/npm/pypi/docker/go/custom), monorepo workspace discovery, versionfiles/stagefiles mapping, and post-release patterns. Language-specific build targets live in scaffold-rust…
setup-ci
Defines GitHub Actions workflow structure: ci.yml + release.yml naming, concurrency groups, bot-commit skip, workflowcall reuse, App-token checkout, and optional fsrc/teasr steps. Language-specific pipelines live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform. Use when setting up…