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-automate-enablegit 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-automate-enable)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-automate-enable"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-automate-enable/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-automate-enable"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-automate-enable.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.00101 | $0.01508 |
| Opus 5 | $0.00051 | $0.00754 |
| Sonnet 5 | $0.00020 | $0.00302 |
| Haiku 4.5 | $0.00010 | $0.00151 |
Grade A, and why
clockify-automate-enable 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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify automate enable
Resume after a pause. Confirm, then flip live-automation flags on and restore Cursor glue from preserved yaml. Do not re-run forge / Cursor / runaway wizards unless required fields are missing.
First-time automation or after /clockify-unautomate: clockify-automate. Temporary pause: clockify-automate-disable.
Config root
Pass config_root on Clockify MCP calls. If it is already known this session and still this repo, reuse it. Otherwise resolve once with git rev-parse --show-toplevel from the working directory (same rules as automate).
Prerequisites
- Load config (
clockify_get_configwithconfig_root). If missing, runclockify-initis not enough for automate — tell the user to run/clockify-automate(full wizards). Stop. - Init / after unautomate (all
forge.*.enabledfalse, typically empty triggers / empty modes): settings were never kept. Chat that enable cannot restore what was rolled back; redirect to/clockify-automate. Do not invent forge/triggers/modes. - Paused (
enabled: falseand anyforge.*.enabledis true): normal enable path below. - Already active (
enabled: trueand anyforge.*.enabledis true): still confirm; refresh rule (and runaway hooks ifsettings.runaway.enabled) from current yaml — idempotent, no wizards unless the user asks to reconfigure (then hand off to/clockify-automate).
Confirm
- Inventory with tools if needed, then repeat the result in a normal chat message (markdown list). Do not rely on tool snippets as the only listing.
- Chat list: what will be restored —
entry.automated.enabled: true,platforms.cursor.enabledwhen modes warrant it, rewrite.cursor/rules/clockify.mdc, and reinstall runaway hooks only ifsettings.runaway.enabledis true. Note forge / triggers / modes already on disk (not re-asked). - Then AskQuestion with only a short confirm, e.g. “Resume Clockify automate from saved settings?” — do not put the inventory in the question box.
- Do not re-run forge / Cursor / runaway AskQuestion wizards on this path.
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.
- 3d ago First seen · 85 lines · 101 tokens per session scan A 370abff244b1
clockify-automate-enable is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 1,508 once invoked, about $0.0005 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-09-09.
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…
gmail-query-syntax
Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose. Read this when constructing a Gmail search query string for the googleworkspace.gmailsearchmessages Code Mode call, especially when filtering by sent vs received, recency, sender, or…