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 felipeelias/claude-notifier --skill releasegit clone --depth 1 https://github.com/felipeelias/claude-notifierWrote 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/felipeelias/claude-notifier/release)<a href="https://agentmods.dev/skills/felipeelias/claude-notifier/release"><img src="https://agentmods.dev/badge/skills/felipeelias/claude-notifier/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.00012 | $0.00484 |
| Opus 5 | $0.00006 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
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 7d 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.
What it actually says
Creating a Release
Releases are created via GitHub Releases. Pushing a tag triggers goreleaser, which builds cross-platform binaries and updates the Homebrew tap.
Current state
- Latest release: !
gh release list --limit 1 --json tagName,publishedAt --template '{{range .}}{{.tagName}} ({{.publishedAt}}){{end}}' - Commits since last release:
!git log $(git describe --tags --abbrev=0)..HEAD --oneline
Steps
1. Verify CI is green on main
gh run list --branch main --limit 3
If any run is in progress, wait with gh run watch <id> --exit-status.
2. Determine next version
Apply conventional commit rules to the commits listed above:
feat:commit present -> minor bump (e.g. v0.1.1 -> v0.2.0)- Only
fix:,refactor:,perf:, etc. -> patch bump (e.g. v0.1.1 -> v0.1.2) - Breaking change (
BREAKING CHANGE:or!:) -> major bump
Confirm the version with the user before proceeding.
3. Write release notes
Group commits by type into a short human-readable summary. Goreleaser auto-generates a detailed changelog from commits (excluding docs:, test:, ci: prefixes), so keep notes high-level.
4. Create the release
gh release create v<VERSION> --title "v<VERSION>" --notes "<NOTES>"
This pushes a tag, which triggers .github/workflows/release.yml -> goreleaser -> builds binaries + updates Homebrew tap.
5. Verify the release workflow
gh run list --limit 1
gh run watch <id> --exit-status
Confirm binaries appear on the release page:
gh release view v<VERSION>
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.
- 7d ago First seen · 63 lines · 12 tokens per session scan A 7c72d222bf80
release is a skill published in the GitHub repository felipeelias/claude-notifier (4 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 484 once invoked, about $0.0001 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-31.
Other skills, from other repositories
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
skill-ship
Package and finalize completed work for delivery — use when a feature is done and ready to ship.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
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"…