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/clockify-uninitnpx skills add dustinestes/clockify-agent-plugin --skill clockify-uninitgit clone --depth 1 https://github.com/dustinestes/clockify-agent-pluginWhat 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 | $0.00075 | $0.00746 |
| Opus 5 | $0.00037 | $0.00373 |
| Sonnet 5 | $0.00015 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
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 2d 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 — 55 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 stop agent-mediated timers and 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.If the stanza still lists the rule path (unautomate not run yet), remove those lines together.
-
After stanza removal: if
.gitignoreis empty or whitespace-only, delete the file (same idea as deleting emptyhooks.jsonin unautomate). If any other ignore rules remain, keep the file. Never delete a non-empty.gitignore. No need to know whether init created the file — emptiness after our stanza is gone is enough.
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.
- 2d 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 9d ago), licensed MIT. It adds 75 tokens to every session and 746 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
goalslot-goal-checkup
Check whether one GoalSlot goal is on track. Use when the user asks about a specific goal, whether they will hit a deadline, why a goal is stalled, or wants to decide between changing the target, moving the deadline, or allocating more time. Shows the arithmetic and distinguishes an allocation problem from an…
smartsheet-rm
Enterprise Agent Skill for orchestrating Resource Management by Smartsheet (10,000ft API) — manage weekly timesheets, reconciliation, project staffing, assignments, capacity planning, and user availability.
goalslot-log-time
Log or correct time in GoalSlot. Use when the user says they forgot to track something, wants to catch up on yesterday or last week, narrates what they worked on, asks to fix or move a time entry, or wants to start and stop the timer. Converts freeform narration into correctly attributed time entries.
goalslot-plan-my-week
Plan a week on the GoalSlot schedule. Use when the user asks to plan their week, block time for a goal, rebalance their schedule, or says they are not making progress on something and wants time set aside for it. Reads which goals are behind pace and what last week actually looked like before proposing blocks.
goalslot-weekly-review
Run a GoalSlot weekly review. Use at the end of a week, or when the user asks how their week went, whether they are on track, what they got done, or wants help writing a reflection. Combines logged hours, goal pace, schedule adherence and the user's own journal and check-ins into one honest read.
sideshift-operations
Use when the user wants to inspect or operate a SideShift company, including UGC campaigns, creators, recruiting, applications, jobs, contracts, posts, analytics, messaging, invoices, payouts, wallet, settings, or other SideShift workflows through the installed MCP server.