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.
git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-codeWrote 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/commands/lucasgaravelli/pm-skills-claude-code/stakeholder-update)<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/stakeholder-update"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/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/commands/lucasgaravelli/pm-skills-claude-code/stakeholder-update"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/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.00000 | $0.02865 |
| Opus 5 | $0.00000 | $0.01432 |
| Sonnet 5 | $0.00000 | $0.00573 |
| Haiku 4.5 | $0.00000 | $0.00286 |
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 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.
This is a copy
100% identical to stakeholder-update — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/stakeholder-update
O que essa skill faz
Transforma notas confusas de sprint em status executivo limpo: situação atual, decisões tomadas, próximos passos, riscos.
Saída: Update de 1-2 páginas pronto para board, exec, ou stakeholders.
Quando usar
- Final de sprint/semana, precisa briefar executivos
- Descoberta importante que afeta roadmap
- Problema ou decisão que precisa escalação
- Board meeting na semana que vem
Input esperado
Mínimo:
- Notas confusas da sprint/descoberta/research
- Contexto: O que stakeholders precisam saber?
- Urgência: É para informar ou para decisão?
Opcional:
- Métricas (churn, engagement, revenue impact)
- Dados de descoberta
- Screenshots ou mockups
- Comparação vs plano
Processo
- Extração de narrativa — Qual é a história aqui?
- Estrutura clara — Situação → Impacto → Recomendação
- Números quando possível — "Impacto de $50k/ano" vs "impacto grande"
- Decisão clara — O que precisa ser decidido?
- Próximos passos — Quem faz o quê até quando?
Output
# Status Update — [Data/Período]
## Executive Summary
[1 parágrafo que resume: situação, impacto, recomendação]
---
## Situation
### What happened
[Contexto do que ocorreu — descoberta, resultado, problema]
### Impact
**On business**: [$ impacto ou métrica]
**On timeline**: [Roadmap shift ou não?]
**On team**: [Resource impact]
### Data points
- [Métrica 1]: [Número]
- [Métrica 2]: [Número]
- [Discovery insight]: [Frase-chave]
---
## Analysis
### What we learned
[3-5 bullets de insight principal]
### Why it matters
[Contexto maior — como isso muda estratégia ou próximos passos?]
### What we considered
[Opções que analisamos — se decisão é necesária]
---
## Recommendation
### Option A: [Opção 1]
**Pros**: [2-3 vantagens]
**Cons**: [2-3 desvantagens]
**Cost**: [$X ou Y weeks]
**Timeline**: [Quando termina]
### Option B: [Opção 2]
**Pros**: [...]
**Cons**: [...]
**Cost**: [...]
**Timeline**: [...]
### Option C: [Opção 3]
**Pros**: [...]
**Cons**: [...]
**Cost**: [...]
**Timeline**: [...]
### Our recommendation
**Go with Option [A/B/C]** because [razão principal].
**Expected outcome**: [Métrica esperada if decidem isso]
---
## Next Steps
| What | Owner | When | Blocker? |
|------|-------|------|----------|
| [Decision needed] | [Role] | [Date] | [If yes] |
| [Action] | [Owner] | [Date] | [If yes] |
| [Communication] | [Owner] | [Date] | |
---
## Risks
| Risk | Mitigação | Monitoring |
|------|-----------|-----------|
| [Risk] | [Como evitar] | [Como detectar] |
---
## Questions?
Contact: [PM name] - [email]
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 · 357 lines · 0 tokens per session scan A 57fa84912bca
stakeholder-update is a command published in the GitHub repository lucasgaravelli/pm-skills-claude-code (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,865 tokens. A static security scan graded it A with 0 findings. It is 100% identical to stakeholder-update, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.