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 agentmods add skills/mpaarating/ai-workflow-kit/eod-reviewnpx 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.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 | $0.00021 | $0.00912 |
| Opus 5 | $0.00010 | $0.00456 |
| Sonnet 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 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.
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.
- 4d 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 3mo ago), licensed MIT. It adds 21 tokens to every session and 912 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…