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/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/tomzx/agents/end-day"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-day.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.00047 | $0.00395 |
| Opus 5.5 | $0.00019 | $0.00158 |
| Sonnet 5.5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
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 22d 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.
- 22d ago Changed · +4 lines e99bfaca8338
- 1mo ago First seen · 40 lines · 47 tokens per session scan A 1f31743df8b3
end-day is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 395 once invoked, about $0.0002 per session on Opus 5.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
OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
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…