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-enter-timenpx skills add dustinestes/clockify-agent-plugin --skill clockify-enter-timegit 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-enter-time)<a href="https://agentmods.dev/skills/dustinestes/clockify-agent-plugin/clockify-enter-time"><img src="https://agentmods.dev/badge/skills/dustinestes/clockify-agent-plugin/clockify-enter-time.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.00542 |
| Opus 5 | $0.00032 | $0.00271 |
| Sonnet 5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade C, and why
clockify-enter-time scanned grade C with 1 finding 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
5. **Times omitted** (forgot to track): infer start from cheap signals — git log / branch checkout, conversation timestamps, recent file edits. End defaults to now unless they give one. **Show the inferred window and con What it actually says
Clockify enter time
Manual method: clockify_create_time_entry with entry_method: manual. Typed times stay exact.
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. Honormanual.description,manual.task,manual.overlap. Do not apply rounding.- Never invent project/task ids.
Workflow
clockify_get_running_timerwithconfig_root. If a timer is already running for this same work, do not double-count — point atclockify-stop-timer.- Resolve project (list/ensure). Resolve task from
manual.task.from/if_missing(same rules as start-timer: prompt, github_label, repo, or none). - Description: ask or use their text (
manual.description.fromis alwaysprompt; no issue templates). - Times given (e.g. 09:30–09:45): convert to ISO and create. Do not round.
- Times omitted (forgot to track): infer start from cheap signals — git log / branch checkout, conversation timestamps, recent file edits. End defaults to now unless they give one. Show the inferred window and confirm. Never silently log hours.
clockify_create_time_entrywithconfig_rootandentry_method: manual. Ifoverlap: true, show the clash. Retry withconfirm_overlap: trueonly if they agree (oron_conflictisoverride). Override is how parallel completed streams can stack; do not treat that as the default.
Examples
User: "Log 9:30 to 10:15 on the login bug"
- Config + running-timer check.
- Create entry with those times, no rounding.
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 · 35 lines · 64 tokens per session scan C 527ea32a1a28
clockify-enter-time is a skill published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 10d ago), licensed MIT. It adds 64 tokens to every session and 542 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). 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.