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-initgit 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-init)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-init"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-init/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-init"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-init.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.00086 | $0.01509 |
| Opus 5.5 | $0.00034 | $0.00604 |
| Sonnet 5.5 | $0.00017 | $0.00302 |
| Haiku 4.5 | $0.00009 | $0.00151 |
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 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clockify init
Pin a workspace and write the v4 base contract so timer and enter-time share one yaml. Config is personal by default (gitignored). Decision map: flows.md.
Next mode: clockify-automate runs the forge + Cursor platforms wizards and writes rules. Do not write those here.
Config root
Pass config_root (absolute git toplevel, or folder root when not a git repo) 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. - Non-git: if
git rev-parsefails, use the folder this Cursor window opened (or the focused folder in a multi-root workspace) asconfig_root. Do not block init — folder name is thelocal_folderfallback.
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 local folder name from that git toplevel (folder name), or the non-git folder name from step 5 above. 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
scope.workspace_idwhen config already exists unless the user asks to change it. - Only fill missing ignore pieces (Always step), then jump to verify + end message.
- Do not rewrite config,
- Otherwise continue with first-time bootstrap below.
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 7f59c3d3611b
- 1mo ago Changed · -79 lines · -25 tokens per session 624cac3b75f9
- 1mo ago Changed · +23 lines 33ed55dc29ee
- 1mo ago 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 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,509 once invoked, about $0.0003 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.
beebole-usage
Guía para manejar bien el MCP de Beebole (control de horas). Úsala SIEMPRE que el trabajo implique Beebole o cualquier tool beebole — fichar/consultar horas, proyectos, tareas, personas, timesheets (aprobar/rechazar) o informes de dedicación y rentabilidad. Explica el flujo correcto (curadas → search/describe/…
workspace-builder
Build ServiceNow App Engine Studio applications — sysscope creation, scoped tables, sysawworkspace with lists/forms, the sysux record chain behind UI Builder workspaces, data brokers, and application export readiness checks. Never create a UI Builder page by inserting a sysuxpage row.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.