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 mpaarating/ai-workflow-kit --skill eod-reviewgit clone --depth 1 https://github.com/mpaarating/ai-workflow-kitWrote 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/mpaarating/ai-workflow-kit/eod-review)<a href="https://agentmods.dev/skills/mpaarating/ai-workflow-kit/eod-review"><img src="https://agentmods.dev/badge/skills/mpaarating/ai-workflow-kit/eod-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/mpaarating/ai-workflow-kit/eod-review"><img src="https://agentmods.dev/badge/skills/mpaarating/ai-workflow-kit/eod-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.00021 | $0.00912 |
| Opus 5.5 | $0.00008 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
eod-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 2mo 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End-of-Day Review
Trigger Phrases
- "eod review"
- "end of day"
- "wrapping up"
- "done for today"
- "signing off"
- "goodnight"
Workflow
Step 1: Read Today's Daily Page
Fetch today's daily page from {{notes}}.
- If no daily page exists, tell the user and offer to create a quick recap from scratch instead.
- Extract the Focus Areas section (the morning plan) for comparison.
- Extract the Working Notes section for context on what actually happened.
Step 2: Gather Task Activity
Query {{tasks}} for tasks that changed status today (completed, moved to in-progress, or newly created).
- Include: task ID, title, old status, new status.
- This gives an objective view of what moved, independent of what the user wrote down.
Step 3: Compare Plan to Outcomes
For each item in the morning Focus Areas:
- Mark as: Done, In Progress, or Not Started.
- If the user worked on things not in the morning plan, note those as Unplanned Work.
Present this as a simple table or checklist so the user can confirm or correct.
Step 4: Categorize the Day
Organize the day's work into four categories:
- Shipped: Work that is complete and delivered (merged PRs, closed tickets, sent deliverables).
- Moved Forward: Work that progressed but isn't done yet (open PRs, in-progress tickets, drafts).
- Blocked: Work that couldn't progress and needs something from someone else.
- Carry Forward: Items to pick up tomorrow, with brief context on where they left off.
Ask the user to confirm or add anything missing from each category.
Step 5: Draft the Recap
Write a concise end-of-day recap. Format:
## End-of-Day Recap
### Shipped
- [item] ([task ID if applicable])
### Moved Forward
- [item] — [current state / next step]
### Blocked
- [item] — blocked on [who/what]
### Tomorrow
- [carry-forward item 1]
- [carry-forward item 2]
- [any new priority for tomorrow]
Step 6: Update the Daily Page
Write the recap into the "End-of-Day Recap" section of today's daily page in {{notes}}.
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.
- 2mo ago First seen · 125 lines · 21 tokens per session scan A 301174675dcd
eod-review is a skill published in the GitHub repository mpaarating/ai-workflow-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 912 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.