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-unautomategit 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-unautomate)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-unautomate"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-unautomate/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-unautomate"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-unautomate.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.00104 | $0.01395 |
| Opus 5.5 | $0.00042 | $0.00558 |
| Sonnet 5.5 | $0.00021 | $0.00279 |
| Haiku 4.5 | $0.00010 | $0.00139 |
Grade A, and why
clockify-unautomate 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify unautomate
Rollback, not a pause. Confirm, then remove Cursor glue and reset only automate-owned yaml to the plugin example defaults. Everything outside entry.automated stays (workspace pin, project, timer, manual).
Temporary disable while keeping forge/platform settings: clockify-automate-disable / clockify-automate-enable.
To remove .clockify/ entirely, use clockify-uninit.
Confirm
- Inventory with tools if needed, then repeat the result in a normal chat message (markdown list of paths). Do not rely on tool snippets as the only listing.
- Chat list: rule + Clockify-owned hooks (including
.cursor/hooks/clockify-runaway.shwhen present), and note empty dirs that will be removed if they become empty after cleanup. Note thatentry.automatedin.clockify/config.ymlwill be reset to example defaults (forge/settings.on_start/modes wiped). The managed.clockify/gitignore line stays.plugin/scope/entry.timer/entry.manualare not touched. - Then AskQuestion with only a short confirm, e.g. “Roll back Clockify automate in this repo?” — do not put the inventory in the question box.
- Do not delete
.clockify/or the managed.clockify/gitignore line. - Do not uninstall the Clockify Agent Plugin unless the user explicitly asks.
Removals
- Delete
.cursor/rules/clockify.mdconly (leave other rules alone). Also delete leftover.cursor/rules/clockify-time.mdcif present — do not leave either file. If.cursor/rules/is then empty, delete the empty directory. Never delete a non-emptyrules/dir or unrelated*.mdcfiles. - Edit
.cursor/hooks.json: drop only Clockify-owned hook entries — those whosecommandreferencesclockify-runaway/.cursor/hooks/clockify-runaway.sh, or that only invoke Clockify tools / were added byclockify-automate. Leave unrelated hooks intact. Delete.cursor/hooks/clockify-runaway.shif present. If the file becomes empty or{}with no remaining hooks, deletehooks.json. If.cursor/hooks/is then empty, delete the empty directory. Never delete unrelated hook scripts or a non-emptyhooks/dir. Do not delete.cursor/wholesale. - If the managed gitignore stanza includes
.cursor/rules/clockify.mdc,.cursor/rules/clockify-time.mdc, or.cursor/hooks/clockify-runaway.sh, remove those lines (the rule/script files are gone). Keep:
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 · +6 lines · +12 tokens per session bc78a08f61dd
- 1mo ago Changed · +44 lines · +34 tokens per session 85fcc9bc63d6
- 2mo ago First seen · 48 lines · 58 tokens per session scan A 6022ad789d61
clockify-unautomate is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,395 once invoked, about $0.0004 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
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.
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.
json-schema-emails
Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.
compact-now
Operator-triggered proactive compaction — Chrono externalizes load-bearing state (active decisions, open tasks, next action) to a snapshot + a durable Vault learning note before invoking Claude Code's native /compact, then resumes from the snapshot. Use when the operator says "/compact-now" / "compact now" or when…