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 KhaledSaeed18/dotclaude --skill release-taggit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/release-tag)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/release-tag"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/release-tag.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.00064 | $0.01229 |
| Opus 5 | $0.00032 | $0.00615 |
| Sonnet 5 | $0.00013 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
release-tag 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Take the repo from "ready" to a clean, tagged, pushed release. Releases are outward-facing and effectively irreversible once published, so every step is gated by pre-flight checks and explicit confirmation.
Hard rules: never break these
- Never release a dirty or unverified tree. Working tree clean, on the correct branch, up to date with the remote, and tests/CI green; all true before tagging.
- Tags are immutable once published. Never move or overwrite a pushed tag; if a release is wrong, cut a new patch version. Force-retagging breaks everyone who already pulled.
- Follow SemVer honestly. The bump must reflect what actually changed (see Step 2), not a convenient number.
- Confirm before the commit, the tag, and the push. These are the irreversible, outward-facing actions.
- No AI/co-author trailers in the release commit or tag message.
- Publishing is downstream. Tagging ≠ publishing to a registry. Don't run
npm publish/cargo publish/ etc. unless explicitly asked; most pipelines publish from CI on tag.
Step 1: Pre-flight
git status→ clean tree (or stash/commit deliberate changes first).- On the release branch (usually
main/masteror arelease/*branch) and synced:git fetch && git statusshows up to date. - Latest tag and history since it:
git describe --tags --abbrev=0. - Tests, linters, and build pass locally; CI on the release commit is green.
Step 2: Determine the version
Derive the SemVer bump from the commits since the last tag:
- MAJOR: any breaking change (
!marker,BREAKING CHANGE:footer, removed/incompatible API). - MINOR: new backward-compatible features (
feat). - PATCH: backward-compatible fixes only (
fix,perf). - Pre-1.0: minor/patch carry the instability caveat; respect the project's stated policy.
- Honor pre-release / build identifiers if used (
1.4.0-rc.1,+build.5) and any explicit version the user gives.
Step 3: Bump the version files (stack-aware)
Update wherever the canonical version lives; detect by the manifests present:
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 · 73 lines · 64 tokens per session scan A 90ee5db56974
release-tag is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 1,229 once invoked, about $0.0003 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
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.