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-unautomatenpx 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.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.00058 | $0.00646 |
| Opus 5 | $0.00029 | $0.00323 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00065 |
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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify unautomate
Mode off. Confirm, then remove Cursor glue only. Leave the repo contract (.clockify/) in place.
To remove config as well, 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 only. Note that
.clockify/and the managed.clockify/gitignore line stay. - Then AskQuestion with only a short confirm, e.g. “Turn off Clockify agent mode 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. -
Edit
.cursor/hooks.json: drop only Clockify-owned hook entries (those that only invoke Clockify tools / were added byclockify-automate). Leave unrelated hooks intact. If the file becomes empty or{}with no remaining hooks, deletehooks.json. -
If the managed gitignore stanza includes
.cursor/rules/clockify.mdcor.cursor/rules/clockify-time.mdc, remove those lines (the rule file is gone). Keep:# Clockify Agent Plugin — personal time-tracking (delete this block to share with the team) .clockify/Normal path: the
.clockify/stanza remains, so leave.gitignorein place. Edge case only: if after removing rule lines the file is empty or whitespace-only, delete it (same as emptyhooks.json). Never delete a non-empty.gitignore. Full stanza teardown (and deleting an emptied file) isclockify-uninit.
Do not
- Wipe unrelated Cursor hooks or rules
- Delete
.clockify/or a non-empty.gitignore - Uninstall Directory / local plugin or clear
CLOCKIFY_API_KEY - Treat tool output as the user-visible inventory (always restate paths in chat before AskQuestion)
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.
- 5d 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 yesterday), licensed MIT. It adds 58 tokens to every session and 646 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
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.
harness-design-fuzzing
Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…
memory-safety-c-cpp
Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…
vulnerability-triage
Reference vocabulary for interpreting vulnerability findings — detector-vs-impact distinction, severity anchoring on demonstrated evidence, the eleven-item interpretation rubric, delegation transparency, primitive-extent scaling, the disqualifier taxonomy (D-0..D-4), CVSS Achievable / Environmental framing…