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-initnpx skills add dustinestes/clockify-agent-plugin --skill clockify-initgit 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.00111 | $0.02261 |
| Opus 5 | $0.00056 | $0.01130 |
| Sonnet 5 | $0.00022 | $0.00452 |
| Haiku 4.5 | $0.00011 | $0.00226 |
Grade A, and why
clockify-init 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 yesterday.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify init
Set up the repo contract so timer and enter-time tools share one yaml. Config is personal by default (gitignored) so product repos stay clean.
Optional next mode: clockify-automate wires Cursor rules/hooks. Do not write those here.
Config root
Pass config_root (absolute git toplevel) 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:
git rev-parse --show-toplevelfrom the working directory (no path argument). Open editor tabs are not required.- If that fails, the same command from the folder this Cursor window opened.
- Multi-root
.code-workspaceonly: git-toplevel the focused file or explorer folder. - Still ambiguous: ask which root, or look for
.clockify/config.ymlunder each root. Do not guess the.code-workspaceparent.
Re-resolve when the user switches folders or the focused root changes.
Idempotency
Re-runs are expected (including from clockify-automate). Treat existing setup as authoritative:
- Confirm MCP auth:
clockify_get_userwithconfig_root(fix if missing API key). - Detect repo name from that git toplevel (folder name). Do not use Cursor’s workspace folder when it is a multi-root
.code-workspaceparent. - If
.clockify/config.ymlexists (orclockify_get_configwithconfig_rootreturnsfound: trueat that path):- Do not rewrite config,
.managed-by-init, or.clockify/.gitignoreunless the user explicitly asks to reset/overwrite. - Do not re-prompt for
workspace_idor shape when config already exists unless the user asks to change them. - Only fill missing ignore pieces (step 11), then jump to verify + conditional ensure (steps 13–17).
- Do not rewrite config,
- Otherwise continue with first-time bootstrap below.
.clockify/.managed-by-init marks layout ownership for clockify-uninit; its presence alone is not required to skip — existing config.yml is the primary “already inited” signal.
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.
- yesterday First seen · 144 lines · 111 tokens per session scan A 0a8953ad7a65
clockify-init is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 8d ago), licensed MIT. It adds 111 tokens to every session and 2,261 once invoked, about $0.0006 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.