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 redhuntlabs/wizard --skill writing-a-status-updategit clone --depth 1 https://github.com/redhuntlabs/wizardWrote 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/redhuntlabs/wizard/writing-a-status-update)<a href="https://agentmods.dev/skills/redhuntlabs/wizard/writing-a-status-update"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/writing-a-status-update/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/redhuntlabs/wizard/writing-a-status-update"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/writing-a-status-update.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.00022 | $0.00604 |
| Opus 5 | $0.00011 | $0.00302 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
writing-a-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 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing a Status Update
What this does
Drafts a short, scannable status update for a manager, board, or team. Headline + wins + blockers + next.
When to use
- Weekly status to your manager
- Monthly project update to stakeholders
- Quarterly board update
- Any recurring "what happened, what's next" message
What you bring (Inputs)
- This period's wins (raw list)
- This period's blockers (with the asks)
- Next period's focus
- Optional: relevant metric
What you get (Output)
A 5-bullet update with a one-sentence headline.
How it works (Steps)
- Write the headline: one sentence naming the most important thing this period.
- List wins as results, not activities. "Shipped X" beats "worked on X."
- List blockers, max 1. For each: name the blocker, name the ask, name the deadline.
- State next period's focus in one sentence.
- Optional: add one metric line.
- Trim ruthlessly to 5 bullets total.
Quality bar
- Under 5 bullets total
- Every win is a result, not an activity
- Every blocker has an explicit ask + deadline
- Headline stands alone (someone could read just it)
- No jargon outside the team's shared vocabulary
Variations
- Board update: add a "decisions needed" section
- Team-internal: add a "shoutouts" line (one or two names with the specific thing)
- Project update: replace wins/blockers with "milestones hit / at-risk / next milestone"
- Rush mode: 3 bullets max — wins + asks only
Example
Input: Wins: shipped onboarding redesign, hired senior PM, fixed billing bug. Blocker: legal review on terms-of-service pending 2 weeks. Next: ship pricing page A/B test.
Output:
Headline: Shipped onboarding redesign + hired senior PM; pricing test is gated on legal.
Wins:
- Shipped onboarding redesign (activation +12% week-1)
- Hired senior PM (Sam, starts Apr 28)
- Fixed billing bug (zero recurrences in 7 days)
Blocker:
- Legal review on new ToS pending 2 weeks. Need: Sara to push by Wed, else pricing test slips a week.
Next: ship pricing page A/B test by EoW.
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 · 78 lines · 22 tokens per session scan A 6a1cda20df7c
writing-a-status-update is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 604 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
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
incident-commander
Coordinate active incidents through severity assessment, roles, mitigation, communications, recovery verification, and postmortem handoff.
interview-system-designer
Design hiring interviews, competency matrices, question banks, scoring rubrics, and interviewer calibration for a specified role.