Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tomzx/agentsnpx agentmods add skills/tomzx/agents/end-of-month-summaryWrote 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-summary)<a href="https://agentmods.dev/skills/tomzx/agents/end-of-month-summary"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-month-summary/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-summary"><img src="https://agentmods.dev/badge/skills/tomzx/agents/end-of-month-summary.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.00026 | $0.01467 |
| Opus 5 | $0.00013 | $0.00733 |
| Sonnet 5 | $0.00005 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
end-of-month-summary 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 9d 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 — 154 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
MONTH_START=!date -d "$(date +%Y-%m-01)" +%Y-%m-%d
MONTH_START_MINUS_ONE=!date -d "$MONTH_START - 1 day" +%Y-%m-%d
NEXT_MONTH_START=!date -d "$(date +%Y-%m-01) + 1 month" +%Y-%m-%d
Generate End-of-Month Summary
Produces a monthly digest covering personal GitHub activity, personal Slack activity, a monitored Slack channel, each colleague's contributions, outstanding action items, and thanks from the month.
Prerequisites
SLACK_TOKEN,SLACK_COOKIE, andSLACK_USERin.env(same credentials used bycollect_individual_threads.py)ghCLI authenticatedsummarize-github-activityscript at$HOME/repos/git/personal-automation/others/summarize-github-activityNOTES_DIRenvironment variable set (resolved via~/.agents/scripts/get-env NOTES_DIR)COLLEAGUESenvironment variable set (resolved via~/.agents/scripts/get-env COLLEAGUES)HELP_ML_CHANNEL_IDenvironment variable set (resolved via~/.agents/scripts/get-env HELP_ML_CHANNEL_ID; Slack channel id for#help-ml-infrastructure)~/.agents/scripts/get-envutility available
Pipeline
GitHub Activity --> {BASE_DIR}/{YEAR}/{MONTH}/github.md
Slack Activity --> {BASE_DIR}/{YEAR}/{MONTH}/slack.md
#help-ml-infra --> {BASE_DIR}/{YEAR}/{MONTH}/slack.help-ml-infrastructure.md
Colleagues --> {BASE_DIR}/{YEAR}/{MONTH}/slack/{COLLEAGUE}.md (parallel)
{BASE_DIR}/{YEAR}/{MONTH}/slack.colleagues.md
Action Items --> {BASE_DIR}/{YEAR}/{MONTH}/action-items.md
Thanks --> {BASE_DIR}/{YEAR}/{MONTH}/thanks.md
Steps
1. Summarize GitHub Activity
$HOME/repos/git/personal-automation/others/summarize-github-activity tomzx {MONTH_START} {TODAY} Shopify,shop
Write output to {BASE_DIR}/{YEAR}/{MONTH}/github.md.
2. Summarize Personal Slack Activity
Summarize .slack.md files in {BASE_DIR}/{YEAR}/{MONTH}/ from the month ending {TODAY}. Write to {BASE_DIR}/{YEAR}/{MONTH}/slack.md:
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.
- 9d ago First seen · 154 lines · 26 tokens per session scan A 8dd2ae76bba2
end-of-month-summary is a skill published in the GitHub repository tomzx/agents (8 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,467 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.