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 tomzx/agents --skill end-daygit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/end-day)<a href="https://agentmods.dev/skills/tomzx/agents/end-day"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-day.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.1 | $0.00047 | $0.00391 |
| Opus 5 | $0.00023 | $0.00196 |
| Sonnet 5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
end-day 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 4d 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.
What it actually says
End Day
This skill orchestrates the end-of-day pipeline.
Instructions
- Read and follow end-of-day-summary in full (same outputs, same pipeline, same prerequisites).
- If the user asks for reflection, goal alignment, or a review (not just a summary), also follow end-of-day-review after the summary files exist or when summary data is unavailable.
- Run identify-skill-gaps every time, after the summary (and review, if run).
- Check whether
SEND_DAILY_SLACKis set (via~/.agents/scripts/get-env SEND_DAILY_SLACK). Only post when it resolves to a truthy value (1,true,yes). If unset or empty, skip this step and inform the user that the Slack update was skipped.
When enabled, post a brief end-of-day summary to the tom-rochette-updates channel using the post-slack-message skill:
uv run post_slack_message.py --channel C0BE3BM97B7 "<summary>"
Format the message as a short wrap-up of what was accomplished today and the next-day standup bullets. Use Slack mrkdwn formatting. Example:
*End of day - {TODAY}*
*Done today:*
- <accomplishment 1>
- <accomplishment 2>
*Tomorrow:*
- <next-day bullet 1>
- <next-day bullet 2>
Report the posted permalink back to the user.
Do not invent a separate EOD format; stay consistent with end-of-day-summary templates.
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.
- 4d ago First seen · 40 lines · 47 tokens per session scan A 1f31743df8b3
end-day is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 391 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-09-03.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…