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-of-month-reviewgit 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-of-month-review)<a href="https://agentmods.dev/skills/tomzx/agents/end-of-month-review"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-month-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/tomzx/agents/end-of-month-review"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-month-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.01556 |
| Opus 5 | $0.00017 | $0.00778 |
| Sonnet 5 | $0.00007 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
end-of-month-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 8d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BASE_DIR=!~/.agents/scripts/get-env NOTES_DIR
TODAY=!date +%Y-%m-%d
YEAR=!date +%Y
MONTH=!date +%m
MONTH_NAME=!date +%B
PREV_MONTH=!date -d "last month" +%m
PREV_MONTH_NAME=!date -d "last month" +%B
End-of-Month Review
Guides a structured monthly retrospective that connects work patterns to goals and OKRs, surfaces trends in time and attention allocation, assesses team trajectory, and produces concrete focus adjustments for the next month.
Prerequisites
NOTES_DIRenvironment variable set (resolved via~/.agents/scripts/get-env NOTES_DIR)~/.agents/scripts/get-envutility available- Optional: weekly
review.mdfiles from the month in{BASE_DIR}/{YEAR}/weekly/ - Optional:
{BASE_DIR}/goals.mdwith current goals and OKRs - Optional:
{BASE_DIR}/team-goals.mdwith current team goals and OKRs - Optional:
{BASE_DIR}/{YEAR}/weekly/*/action-items.mdfiles from the month
Steps
1. Gather Context
Read the following files if they exist:
- All
review.mdfiles from this month's weekly folders in{BASE_DIR}/{YEAR}/weekly/ - All
action-items.mdfiles from this month's weekly folders {BASE_DIR}/goals.md{BASE_DIR}/team-goals.md{BASE_DIR}/{YEAR}/{PREV_MONTH}/month-review.md(last month's review, for continuity)
2. Synthesize Monthly Patterns
Aggregate data across the month's weekly reviews to identify:
Time allocation trend: Average and trend (improving/declining) across the four weeks for (a) goal-driven deep work, (b) collaboration, (c) reactive work, (d) overhead. Flag any week that was a significant outlier.
Goal trajectory: For each goal in goals.md and team-goals.md, reconstruct weekly progress to show the trajectory across the month. Identify goals with no movement (stalled), linear progress, or accelerating progress.
Carried-forward actions: List any action items that appeared in multiple weekly reviews without resolution. These are the items that keep getting deferred.
Decisions avoided: Aggregate any decisions flagged as avoided across the month's reviews.
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.
- 8d ago First seen · 160 lines · 34 tokens per session scan A de787de95c4c
end-of-month-review is a skill published in the GitHub repository tomzx/agents (8 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 1,556 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…