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/kintecus/build/status-updatenpx skills add kintecus/build --skill status-updategit clone --depth 1 https://github.com/kintecus/buildWrote 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/kintecus/build/status-update)<a href="https://agentmods.dev/skills/kintecus/build/status-update"><img src="https://agentmods.dev/badge/skills/kintecus/build/status-update.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.00033 | $0.00293 |
| Opus 5 | $0.00016 | $0.00147 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
status-update 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 3d 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.
What it actually says
Status Update
Draft a stakeholder update from the project's current context.
Context gathering
Before drafting, read:
- The project's
STATUS.mdfor current state - Recent files in
decisions/for key decisions - Recent files in
comms/for prior updates and context
Output format
Draft a concise status update covering:
- Progress: What moved forward since the last update
- Decisions: Key decisions made and their rationale (brief)
- Blockers/risks: What's stuck or at risk, and what's being done about it
- Next steps: What's coming, with rough timeline
Tone and style
- Professional but not corporate. Clear, specific, no fluff.
- Assume the audience is busy and technical.
- Lead with the most important information.
- Under 300 words unless the user says otherwise.
- No process theater - skip anything that doesn't inform or require action.
After drafting
Present the draft for review. Ask if the tone, level of detail, and emphasis are right for the specific audience. Adjust based on feedback.
Save the final version to comms/ with date prefix: YYYY-MM-DD-status-update.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.
- 3d ago First seen · 40 lines · 33 tokens per session scan A 7eaa94fde244
status-update is a skill published in the GitHub repository kintecus/build (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 293 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-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…