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/mitodl/agent-kit/generate-standupnpx skills add mitodl/agent-kit --skill generate-standupgit clone --depth 1 https://github.com/mitodl/agent-kitWhat 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.00106 | $0.07647 |
| Opus 5 | $0.00053 | $0.03823 |
| Sonnet 5 | $0.00021 | $0.01529 |
| Haiku 4.5 | $0.00011 | $0.00765 |
Grade B, and why
generate-standup scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
&& chmod 700 "${XDG_CACHE_HOME:-$HOME/.cache}/generate-standup" \ How it starts
The opening of the file, as written. The whole thing — 660 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Daily Standup
Produces a daily standup post from live GitHub activity and optionally posts it
to the mitodl/hq Check-ins discussion.
Requires: gh (authenticated) and jq.
Step 1 — Fetch GitHub context
Run the bundled context script before asking any questions:
bash skills/process/generate-standup/scripts/get-standup-context.sh [-t YYYY-MM-DD] [-o org1,org2]
| Flag | Description | Default |
|---|---|---|
-t |
"Today" date (YYYY-MM-DD) |
today (UTC) |
-o |
Comma-separated orgs to search | mitodl,openedx |
The script outputs a JSON object:
{
"meta": {
"username": "string",
"display_name": "string",
"today": "string",
"yesterday": "string",
"tomorrow": "string",
"since": "string"
},
"checkin_targets": { "eod": {...}, "bod": {...}, "latest": {...} },
"prs_authored": [...],
"prs_reviewed": [...],
"issues": [...],
"discussions_opened": [...],
"discussion_comments": [...]
}
meta.display_nameis the GitHub profile name when available; fall back tometa.usernameif it is blank.meta.yesterdayis the previous weekday (Friday if today is Monday).meta.tomorrowis the next weekday (Monday if today is Friday).meta.sinceis midnight UTC onmeta.yesterday— the fetch window start.checkin_targetsholds the candidate post targets inmitodl/hq, each withid(GraphQL node ID),number,title,url,createdAt,date(the calendar date the title names) andcomment_count. Any of the three may benull. See Choosing the post target.discussions_opened— discussions the user opened in the window, any category. Opening one is announcement-worthy; see Step 3.discussion_comments— comments and replies the user left in the window, with aurldeep-linked to the comment and a 300-charexcerpt. Check-ins threads are excluded (those are standup posts — reporting them is circular).- Do not infer or fabricate activity beyond what the script returns.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 660 lines · 106 tokens per session scan B c57c53c7ab0a
generate-standup is a skill published in the GitHub repository mitodl/agent-kit (2 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 106 tokens to every session and 7,647 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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…