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 hamzafarooq/claude-code-starter --skill stakeholder-updategit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/stakeholder-update)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/stakeholder-update"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/stakeholder-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/hamzafarooq/claude-code-starter/stakeholder-update"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/stakeholder-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.00048 | $0.00345 |
| Opus 5.5 | $0.00019 | $0.00138 |
| Sonnet 5.5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
stakeholder-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 1mo 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
Ask the user:
- "Paste your raw notes — bullet points, Slack messages, anything."
- "Who is the audience — direct manager, exec team, cross-functional partners, board?"
- "What's the tone — formal written update, or conversational Slack message?"
Then produce:
[Product/Team] Update — [Date or Period]
Status: 🟢 On track / 🟡 At risk / 🔴 Blocked (Choose one and note the reason if not green)
Progress this period
3–5 bullets. What shipped, what moved, what was decided. Lead with the most important thing first. Use past tense.
Blockers & risks
What is slowing progress or could derail the plan. Be specific — vague blockers don't get unblocked. Format: [What is blocked] → [What you need] → [By when]
Decisions needed from this audience
Be explicit. If you need something from the reader, say so directly with a deadline.
Next period focus
3 bullets on what the team is doing next. Enough context to make sense without a full briefing.
Formatting rules:
- Lead with status, not pleasantries
- No passive voice
- No sentence longer than 20 words
- If the audience is exec-level, cut the update by 30% after drafting
Ask: "Want a shorter Slack-friendly version of this?"
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.
- 1mo ago First seen · 44 lines · 48 tokens per session scan A cc0bb6643385
stakeholder-update is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 48 tokens to every session and 345 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.