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-weekly-reviewgit 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-weekly-review)<a href="https://agentmods.dev/skills/zeeshanadilbutt/goalslot-mcp/goalslot-weekly-review"><img src="https://agentmods.dev/badge/skills/zeeshanadilbutt/goalslot-mcp/goalslot-weekly-review/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-weekly-review"><img src="https://agentmods.dev/badge/skills/zeeshanadilbutt/goalslot-mcp/goalslot-weekly-review.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.00073 | $0.00930 |
| Opus 5 | $0.00036 | $0.00465 |
| Sonnet 5 | $0.00015 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
goalslot-weekly-review 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 12d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly review in GoalSlot
The value here is judgement, not arithmetic. The tools already compute the totals. Your job is to say what actually happened, including the part the user would rather not hear.
Sequence
goalslot_get_context. Notetoday,timezoneandcurrentWeek.goalslot_get_reportwithview: "day_total",preset: "this_week". Total minutes and the shape of the week, day by day.goalslot_get_reportwithview: "summary",groupBy: "goal",preset: "this_week". Where the hours went.- The same call again with
preset: "last_week". Without the comparison, a number is not a finding. goalslot_get_reportwithview: "schedule",preset: "this_week". Planned against logged, per recurring block. This is the only thing that distinguishes "never allocated the time" from "allocated it and did not use it".goalslot_list_goalswithincludeStats: true. Pace againsttargetHoursand anydeadline.goalslot_get_journalover the same week. Mood, energy, focus, and the user's ownworkedandblockednotes.goalslot_list_taskswithstatuses: ["DONE"]if the user thinks in tasks rather than hours.
Writing the review
State the exact date range the reports covered. Not "this week": "Monday 18 August to Sunday 24 August".
Then, in this order:
- What moved. Name the two goals that gained the most hours, with the numbers, and how that compares to last week.
- What did not. Name the goal that got the least, or nothing. Do not bury it. Do not soften it into "you made some progress on X" when X got 20 minutes.
- Why, where the data says why. Cross-reference the schedule adherence rows against the days with the least logged time, and against the check-in
energyandfocusscores. A goal at 0 percent adherence on a day the user rated energy 1 is a different story from one at 0 percent on a day they rated energy 5. - Their words, not yours. Quote the
workedandblockednotes verbatim. Paraphrasing a person's reflection back at them as if it were your insight is worse than useless.
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.
- 12d ago First seen · 46 lines · 73 tokens per session scan A b14bb37b0fc7
goalslot-weekly-review is a skill published in the GitHub repository ZeeshanAdilButt/goalslot-mcp (0 stars, last pushed 18d ago), licensed MIT. It adds 73 tokens to every session and 930 once invoked, about $0.0004 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.