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 ZeeshanAdilButt/goalslot-mcp --skill goalslot-log-timegit clone --depth 1 https://github.com/ZeeshanAdilButt/goalslot-mcpWrote 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/zeeshanadilbutt/goalslot-mcp/goalslot-log-time)<a href="https://agentmods.dev/skills/zeeshanadilbutt/goalslot-mcp/goalslot-log-time"><img src="https://agentmods.dev/badge/skills/zeeshanadilbutt/goalslot-mcp/goalslot-log-time/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/zeeshanadilbutt/goalslot-mcp/goalslot-log-time"><img src="https://agentmods.dev/badge/skills/zeeshanadilbutt/goalslot-mcp/goalslot-log-time.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.00070 | $0.01119 |
| Opus 5 | $0.00035 | $0.00560 |
| Sonnet 5 | $0.00014 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
goalslot-log-time 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 11d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log and correct time in GoalSlot
Catching up on untracked time is the highest-frequency real chore in this system. Getting it wrong quietly corrupts goal progress, because every entry with a goalId increases that goal's logged hours.
Units, dates, and the two mistakes that matter
- Everything is whole minutes.
durationMinutes: 90is an hour and a half. There is no hours field on a time entry. The only field anywhere measured in hours is a goal'stargetHours. - Dates are
YYYY-MM-DD, in the user's timezone. Get today fromgoalslot_get_context.today. Do not use your own sense of the date, and never send a timestamp where a date is expected. - Mistake one: logging hours as minutes, or the reverse. Guard against it by restating in both units when you confirm: "3 hours, so 180 minutes, on Monday the 24th."
- Mistake two: the late-night off-by-one. Work that started at 23:30 on Monday belongs to Monday. If you pass
startedAt, the tool checks that its calendar date in the user's timezone matchesdateand rejects the call if not.
Live timer
The timer is server state, shared with the GoalSlot web and mobile apps. Whatever is running there is what goalslot_get_context.runningTimer shows.
goalslot_start_timerwith ataskNameand, when it belongs to one, agoalId.- If a timer is already running you get
TIMER_ALREADY_RUNNINGwith what it is tracking and its elapsed minutes. Do not passtakeOverto get past this. Take-over discards the running session and its time is never written anywhere. Show the user what is running and let them pick: stop it (saves the time) or replace it (throws it away). goalslot_stop_timerconverts the session into a time entry.discard: truewrites nothing.- A session left open longer than 12 hours reports
isStale. Stopping it writes 12 hours, not the real elapsed time, and the response sayscapped: true. Tell the user rather than letting a fake 12-hour entry stand.
Catching up on untracked time
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.
- 11d ago First seen · 49 lines · 70 tokens per session scan A d37e9c8ee71c
goalslot-log-time is a skill published in the GitHub repository ZeeshanAdilButt/goalslot-mcp (0 stars, last pushed 18d ago), licensed MIT. It adds 70 tokens to every session and 1,119 once invoked, about $0.0003 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
clockify-automate
Turn on agent-mediated Clockify tracking: if .clockify/config.yml is missing, run minimal clockify-init first, then forge wizard (GitHub) + Cursor Plan/Debug platforms + runaway wizard, ensure project/tasks, write Cursor rules, and when runaway is enabled install Clockify-owned runaway hooks. Use when the user wants…
clockify-automate-disable
Temporarily pause agent-mediated Clockify tracking without wiping settings: remove the clockify Cursor rule and Clockify-owned runaway hooks, set entry.automated.enabled false and platforms.cursor.enabled false, but keep forge, settings.onstart, triggers, settings.runaway prefs, and modes. Distinct from…
clockify-unautomate
Full rollback of agent-mediated Clockify tracking: remove the clockify Cursor rule and Clockify-owned hooks, and reset entry.automated in .clockify/config.yml to init/example defaults (all forge..enabled false, empty triggers, platforms.cursor off, modes cleared). Does not change plugin, scope, timer, or manual. Use…
clockify-automate-enable
Resume agent-mediated Clockify tracking after clockify-automate-disable: set entry.automated.enabled true, restore platforms.cursor.enabled from preserved modes, rewrite .cursor/rules/clockify.mdc, and reinstall runaway hooks when settings.runaway.enabled is still true. Skips forge/Cursor/runaway wizards unless…
clockify-start-timer
Start a Clockify running timer for the current repo. Use when the user asks to start tracking, clock in, or start a timer on an issue. Honors the timer block in .clockify/config.yml. Warns before stopping a different running timer. Optional backdated start.
clockify-stop-timer
Stop the currently running Clockify timer. Use when the user asks to stop tracking, clock out, or finish an issue/PR in this session. Honors timer rounding and overlap. Does not summarize the whole day.