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 nota-america/forgecat-agent-profiles --skill stakeholder-updategit clone --depth 1 https://github.com/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/stakeholder-update)<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/stakeholder-update"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/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/nota-america/forgecat-agent-profiles/stakeholder-update"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/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.00053 | $0.03273 |
| Opus 5 | $0.00026 | $0.01636 |
| Sonnet 5 | $0.00011 | $0.00655 |
| Haiku 4.5 | $0.00005 | $0.00327 |
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
95% identical to stakeholder-update — 9 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Update
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (
.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_product-management/CONNECTORS.md).
Generate a stakeholder update tailored to the audience and cadence.
Usage
/stakeholder-update $ARGUMENTS
Workflow
1. Determine Update Type
Ask the user what kind of update:
- Weekly: Regular cadence update on progress, blockers, and next steps
- Monthly: Higher-level summary with trends, milestones, and strategic alignment
- Launch: Announcement of a feature or product launch with details and impact
- Ad-hoc: One-off update for a specific situation (escalation, pivot, major decision)
2. Determine Audience
Ask who the update is for:
- Executives / leadership: High-level, outcome-focused, strategic framing, brief
- Engineering team: Technical detail, implementation context, blockers, decisions needed
- Cross-functional partners: Context-appropriate detail, focus on shared goals and dependencies
- Customers / external: Benefits-focused, clear timelines, no internal jargon
- Board: Metrics-driven, strategic, risk-focused, very concise
3. Pull Context from Connected Tools
If ~~project tracker is connected:
- Pull status of roadmap items and milestones
- Identify completed items since last update
- Surface items that are at risk or blocked
- Pull sprint or iteration progress
If ~~chat is connected:
- Search for relevant team discussions and decisions
- Find blockers or issues raised in channels
- Identify key decisions made asynchronously
If ~~meeting transcription is connected:
- Pull recent meeting notes and discussion summaries
- Find decisions and action items from relevant meetings
If ~~knowledge base is connected:
- Search for recent meeting notes
- Find decision documents or design reviews
If no tools are connected, ask the user to provide:
- What was accomplished since the last update
- Current blockers or risks
- Key decisions made or needed
- What is coming next
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 · 356 lines · 53 tokens per session scan A ed787294c3f5
stakeholder-update is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 3,273 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to stakeholder-update, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.
maggy
Maggy is a local AI engineering command center. AI-prioritized inbox across issue trackers (GitHub Issues/Asana), one-click TDD execute with iCPG context enrichment, daily competitor intelligence briefing.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
executar-minha-revisao-operacional
Reúna o que foi entregue e o que avançou em toda a sua superfície operacional. Escolha o que você precisa: uma revisão semanal que agrega a saída de cada habilidade, cruza prioridades e renovações, sinaliza lacunas e recomenda o próximo movimento; ou um resumo de métricas que percorre cada métrica monitorada, calcula…