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-stop-timernpx skills add dustinestes/clockify-agent-plugin --skill clockify-stop-timergit 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.00049 | $0.00384 |
| Opus 5 | $0.00024 | $0.00192 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
clockify-stop-timer 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.
What it actually says
Clockify stop timer
Interactive Timer method (entry_method: timer).
Config-aware behavior
- If
config_rootis already known this session and still this repo, reuse it. Otherwise resolve once withgit rev-parse --show-toplevelfrom the working directory (open tabs are not required; multi-root: focused path only as a tie-breaker). Re-resolve when the folder or focused root changes. Pass that string on Clockify MCP calls — do not run git before every tool. clockify_get_configwithconfig_root. Honortimer.rounding,timer.include_seconds, andtimer.overlap.- Never invent ids.
Workflow
clockify_get_running_timerwithconfig_root. If none, say so. Point atclockify-enter-timeif they meant to log a range they forgot to start.clockify_stop_timerwithconfig_rootandentry_method: timer.- If the tool returns
overlap: true, show the colliding entries. Retry withconfirm_overlap: trueonly if they agree (oron_conflictisoverride). - Report description, project, duration, and rounding metadata from the response. Do not dump a full-day summary (that is
clockify-summarize).
Examples
User: "Stop tracking" / "We shipped the PR"
clockify_stop_timerwithconfig_rootandentry_method: timer.
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 · 31 lines · 49 tokens per session scan A 7f0e576dc719
clockify-stop-timer is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 384 once invoked, about $0.0002 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.