stakeholder-update

stakeholder-update is a command for Claude Code from bjorn-ingmanson/thefroject-plugins. It costs 0 tokens per session (239 once invoked), scanned A, original, MIT.

A command that drafts a short project status update for a chosen audience, such as a team, leadership group, board, or client.

In plain words
What is it for?
Use it to summarize completed work, current focus, blockers, risks, next steps, and requests for help.
Why use it?
It turns recent work and risks into a structured update so readers can quickly understand progress and needed action.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the thefroject-customer-success plugin — 47 skills, 11 commands shipped together

Good fit Use it to summarize completed work, current focus, blockers, risks, next steps…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/bjorn-ingmanson/thefroject-plugins/stakeholder-update
Install

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.

Clone the repo
git clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-plugins

Made for: Claude Code.

Or install thefroject-customer-success, the plugin that ships this one along with the rest of its 47 skills, 11 commands.

Wrote 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.

agentmods badge for stakeholder-update

README.md
[![agentmods](https://agentmods.dev/badge/commands/bjorn-ingmanson/thefroject-plugins/stakeholder-update.svg)](https://agentmods.dev/commands/bjorn-ingmanson/thefroject-plugins/stakeholder-update)
Your own site
<a href="https://agentmods.dev/commands/bjorn-ingmanson/thefroject-plugins/stakeholder-update"><img src="https://agentmods.dev/badge/commands/bjorn-ingmanson/thefroject-plugins/stakeholder-update.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 239 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00239
Opus 5 $0.00000 $0.00120
Sonnet 5 $0.00000 $0.00048
Haiku 4.5 $0.00000 $0.00024

Measured 6d ago against content hash 8477f0a24369, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 6d 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.

customer-success/commands/stakeholder-update.md · 40 lines

What it actually says

/stakeholder-update — Stakeholder Update

Draft a concise status update for stakeholders.

Workflow

  1. Gather context — Read recent git activity, task updates, context files
  2. Identify audience — Who is this for? (team, leadership, board, client)
  3. Draft update — Using the format appropriate for the audience

Format

For leadership/board (under 150 words)

TL;DR: [One sentence headline] Status: 🟢 On track / 🟡 At risk / 🔴 Blocked

Progress:

  • [Completed item with impact]

Next:

  • [Planned item with timeline]

Risks:

  • [Risk with mitigation]

Ask:

  • [Specific help needed]

For team (under 100 words)

Done: [What shipped] Doing: [Current focus] Blocked: [What needs unblocking]

Verification

  • Is the most important news first?
  • Would the reader know what action to take?
  • Are numbers and dates accurate?

Usage: /stakeholder-update [audience] [project or scope]

Changes

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.

  1. 6d ago First seen · 40 lines · 0 tokens per session scan A 8477f0a24369

Subscribe to this mod's changes

stakeholder-update is a command published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 239 tokens. 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.