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 dustinestes/clockify-agent-plugin --skill clockify-uninitgit 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/clockify-uninit)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-uninit"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-uninit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-uninit"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-uninit.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.00819 |
| Opus 5.5 | $0.00034 | $0.00328 |
| Sonnet 5.5 | $0.00017 | $0.00164 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
clockify-uninit 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify uninit
Full local teardown of Clockify-owned files in a consumer repo. Confirm with the user before deleting.
If they only want to pause agent-mediated timers and keep forge/platform settings, stop and run clockify-automate-disable instead.
If they want to stop agent mode and reset automate yaml toward init defaults (keep .clockify/config.yml), stop and run clockify-unautomate instead.
Confirm
- Inventory with tools if needed, then repeat the result in a normal chat message the user can read without opening tool output. Use a short markdown list of paths that exist (and optionally “not found” for expected paths). Tool snippets / terminals are not the inventory.
- That chat list is the confirm surface: unautomate paths plus
.clockify/, the remaining gitignore stanza, and.gitignoreitself if removing the stanza would leave the file empty. Note that the Clockify Agent Plugin stays installed unless they ask otherwise. - If
.clockify/.managed-by-initis missing, still include those well-known paths in the chat inventory (user may have edited by hand). - Then AskQuestion with only a short confirm, e.g. “Remove Clockify files from this repo?” — do not put the inventory in the question box, and do not skip the chat list.
- Do not uninstall the Clockify Agent Plugin unless the user explicitly asks.
Removals
Perform clockify-unautomate first (rule + Clockify-owned hooks + rule gitignore line), then:
-
Delete
.clockify/entirely (config, marker, self-ignore, any extras). -
Remove the remaining managed gitignore stanza when present (idempotent match on either comment header):
# Clockify Agent Plugin — personal time-tracking (delete this block to share with the team) .clockify/Also match the older header
# Clockify MCP — personal time-trackingif a repo was inited before the rename.
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.
- 1mo ago Changed · +3 lines · +11 tokens per session 32060ff28f56
- 1mo ago Changed 90439aa4dfac
- 2mo ago First seen · 55 lines · 75 tokens per session scan A 7792ac9f1271
clockify-uninit is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 819 once invoked, about $0.0003 per session on Opus 5.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, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
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.
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
fluent-brownfield-migration
This skill should be used when the user asks to "convert this app to fluent", "migrate a scoped app to source control", "modernize this servicenow app", "bring an existing app into git", "transform to fluent", or mentions "brownfield" migration of an existing ServiceNow scoped application to the ServiceNow SDK /…