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-automategit 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)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-automate"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-automate/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"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-automate.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.00096 | $0.04632 |
| Opus 5.5 | $0.00038 | $0.01853 |
| Sonnet 5.5 | $0.00019 | $0.00926 |
| Haiku 4.5 | $0.00010 | $0.00463 |
Grade A, and why
clockify-automate 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify automate
Mode on. This is not a second init. Wizards configure forge + Cursor platforms + runaway, patch yaml, ensure Clockify resources, write Cursor glue, and install Clockify-owned runaway hooks when enabled.
Config root
Pass config_root on Clockify MCP calls. If it is already known this session and still this repo, reuse it — do not run git before every tool. Otherwise resolve once with git rev-parse --show-toplevel from the working directory (open tabs are not required). Non-git: use the Cursor window folder (same as init). In a multi-root workspace, git-toplevel the focused file/folder; if nothing is focused, ask or scan roots for .clockify/config.yml. Re-resolve when the focused root changes. Do not pass the .code-workspace parent.
Init first (if needed)
If .clockify/config.yml is missing (clockify_get_config with config_root returns found: false), perform clockify-init (workspace AskQuestion only, write v4 base yaml, ignore markers). It is idempotent. Then continue below. Do not restate or fork that skill’s config/ignore steps.
If config already exists, do not overwrite the whole file — patch only the entry.automated (and scope.project when the forge wizard sets it) fields below.
Paused resume: If any entry.automated.forge.*.enabled is true and root enabled is false (after /clockify-automate-disable), skip the wizards below unless the user asks to reconfigure. Set enabled: true, restore platforms.cursor.enabled when modes warrant it, rewrite Cursor rules, and install/remove runaway hooks per settings.runaway.enabled — same as clockify-automate-enable. Temporary pause without wizards: that skill pair.
Forge wizard
Skip this wizard only when any entry.automated.forge.*.enabled is already true, unless the user asks to reconfigure forge settings. After /clockify-unautomate, all forge.*.enabled are false — always run the full wizard. After /clockify-automate-disable, forge *.enabled flags stay — skip and treat like enable (flip root enabled on + refresh glue) unless they ask to reconfigure.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +5 lines e7bd6bab45aa
- 1mo ago Changed · +209 lines · +14 tokens per session 8165ee505f6f
- 1mo ago Changed · +4 tokens per session 1b893d36992f
- 1mo ago First seen · 74 lines · 78 tokens per session scan A ba4bc8f7301e
clockify-automate is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 4,632 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
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.
managing-reminders
Create and manage PostHog reminders — private, human-paced nudges that fire as in-app notifications on a schedule, optionally linked to a PostHog resource. Use when the user says "remind me to…", wants a one-off or recurring nudge (daily/weekly/monthly/yearly, a cron schedule, or a specific date/time), wants to be…
stellary-mcp
Use Stellary, the AI-native project piloting SaaS, through its hosted remote MCP. Discover projects, boards, cards, documents, cockpit state, and governed agent missions. Use when the user mentions Stellary, Stellary boards, cockpit/pilotage, agent missions, or connecting an assistant to live Stellary work.
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.