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/standupnpx skills add mpaarating/ai-workflow-kit --skill standupgit clone --depth 1 https://github.com/mpaarating/ai-workflow-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.00015 | $0.00945 |
| Opus 5 | $0.00008 | $0.00473 |
| Sonnet 5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
standup 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 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.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Async Standup
Trigger Phrases
- "standup"
- "post update"
- "async update"
- "progress update"
- "team update"
Workflow
Step 1: Gather Work Context
Query {{tasks}} for the user's in-progress and recently completed items.
- In Progress: Tasks with "In Progress" or equivalent status, assigned to the user.
- Recently Completed: Tasks completed since the last standup (or in the last 2 days if no prior standup is found).
- Include: task ID, title, status.
If {{tasks}} is not configured, check today's daily page in {{notes}} for context instead. If neither is available, ask the user what they're working on.
Step 2: Collect Updates Per Item
For each in-progress item, ask the user:
- Progress: What did you do on this? (one line)
- Next: What's the next step? (one line)
- Blocked?: Anything blocking progress? (yes/no, and on whom if yes)
For recently completed items, just note them as done.
Quick mode: If the user provides all context inline (e.g., "standup: finished auth migration, working on PR review, blocked on deploy access"), parse it directly and skip the interactive questions.
Step 3: Format the Update
Draft the standup message using this structure:
**Done:**
- [task title] ([task ID])
- [task title] ([task ID])
**In Progress:**
- [task title] ([task ID]) — [progress note]. Next: [next step].
**Blocked:**
- [task title] ([task ID]) — blocked on [who/what]
[optional: one-line note about priorities or availability]
Rules:
- Keep each bullet to one line.
- Always include task IDs when available — they make updates searchable.
- If nothing is blocked, omit the Blocked section entirely.
- If the user mentions availability changes (OOO, half-day, meetings), add a brief note at the end.
Step 4: Preview and Confirm
Show the formatted message to the user and ask for confirmation before posting.
- Let them edit, add, or remove items.
- Don't post until they say it's good.
Step 5: Post to Team Channel
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 · 133 lines · 15 tokens per session scan A 9eafc7ab637f
standup is a skill published in the GitHub repository mpaarating/ai-workflow-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 945 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.