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/dustinestes/clockify-agent-plugin/publish-releasenpx skills add dustinestes/clockify-agent-plugin --skill publish-releasegit clone --depth 1 https://github.com/dustinestes/clockify-agent-pluginWrote 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/dustinestes/clockify-agent-plugin/publish-release)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/publish-release"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/publish-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.00089 | $0.00532 |
| Opus 5 | $0.00044 | $0.00266 |
| Sonnet 5 | $0.00018 | $0.00106 |
| Haiku 4.5 | $0.00009 | $0.00053 |
Grade A, and why
publish-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 4d 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
Publish a release
Source of truth: docs/publish.md.
Do not start unless asked
Never bump versions, create tags, or open GitHub Releases unless the user asked to publish.
Steps
- Confirm
mainis the intended tree (docs / product work merged as requested). - Confirm
.mcp.jsonis still the unpinned npx shape (never a localdist/path). - Bump the same version in
package.json(and the lockfile),plugin.json, and.cursor-plugin/plugin.json. Tag will bevplus that version.@dustinestes/[email protected]is leftover under the old npm name — do not republish it. First publish of@dustinestes/clockify-agent-pluginmay be0.1.0. npm run check:versions- Commit, open a PR if not already on
main, merge. - After merge:
gh release create vX.Y.Z --generate-notes(not a draft, not a prerelease). - Wait for
.github/workflows/publish.yml. Verifynpm view @dustinestes/clockify-agent-plugin version. - Handshake:
npx -y @dustinestes/clockify-agent-plugin(stdio; idle until Ctrl+C).
Owner-only (stop)
The agent cannot do these. Point at docs/publish.md and wait.
- npm Trusted Publisher (one-time): npmjs.com → package → Trusted Publisher → GitHub Actions, workflow filename
publish.yml. - cursor.directory: first listing is the website form; later skill/catalog changes are Edit, never a second submit. No publisher API.
Directory
Directory snapshots GitHub HEAD and ignores tags. Do not submit the first listing until npm latest matches this tree.
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.
- 4d ago First seen · 40 lines · 89 tokens per session scan A f2010991ff1b
publish-release is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 532 once invoked, about $0.0004 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
Cut a FastMCP release end to end. Use when the maintainer says "cut a release", "prep a patch", "ship 4.x.y", or asks what a release would contain. Covers the notes preview, the title pun, the docs changelog PR that must land before the tag, the tag itself, the publish fan-out, and verifying gofastmcp.com actually…
xcodebuildmcp-docs-release-review
Use when reviewing XcodeBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.
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…
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…
release-dbt-mcp
Release a new version of dbt-mcp to PyPi.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.