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 tomzx/agents --skill brief-stakeholdersgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/brief-stakeholders)<a href="https://agentmods.dev/skills/tomzx/agents/brief-stakeholders"><img src="https://agentmods.dev/badge/skills/tomzx/agents/brief-stakeholders/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/tomzx/agents/brief-stakeholders"><img src="https://agentmods.dev/badge/skills/tomzx/agents/brief-stakeholders.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.00033 | $0.00564 |
| Opus 5 | $0.00016 | $0.00282 |
| Sonnet 5 | $0.00007 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
brief-stakeholders 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brief Stakeholders
Turns PDLC artifacts into communication that decision-makers and stakeholders can act on. Three modes: a single-initiative status update, an exec summary, or a stakeholder map.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - An initiative (
$1) or the portfolio (no argument).
Steps
- Determine the mode from the request:
- Status update — one initiative, current phase and gate history.
- Exec summary — the portfolio or a major initiative, outcomes and asks.
- Stakeholder map — who cares, what they need, and their current stance.
- Read the relevant artifacts:
progress.md, the latest decision records,prd.md,health-report.md,feedback-loop.md, and.pdlc/context/goals.mdfor alignment. - Produce the brief. Lead with the decision or ask, then the one-paragraph rationale, then evidence. Executives read top-down; put the ask first.
- For a stakeholder map, capture each stakeholder's interest, influence, current stance (supporter / neutral / blocker), and what would move them.
- Do not post or send anything. Present the draft. Sending requires explicit user confirmation (commit/push/PR gate).
Output Format
## Status: INIT-N — <title> (<phase>, last gate: <verdict>)
Ask / decision needed: <one line>
Why it matters: <one paragraph, tied to a goal in goals.md>
Evidence: <strongest 1-2 points from artifacts>
Risks: <top risk and mitigation>
Next checkpoint: <date and what will be decided>
### Stakeholder map (if requested)
| Stakeholder | Interest | Influence | Stance | What moves them |
|---|---|---|---|---|
Useful Commands Reference
No CLI commands required. Posting to Slack, email, or GitHub is out of scope for this skill and must be triggered explicitly by the user.
Next Step
If the brief surfaces a needed decision, run make-decision. If it surfaces a kill, run kill-initiative.
Completion Checklist
- The ask or decision is stated in the first line
- Rationale tied to a goal in
goals.md - No artifacts quoted verbatim; synthesized for the audience
- Sending deferred until explicit confirmation
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.
- 6d ago First seen · 57 lines · 33 tokens per session scan A 00a095cf2a5a
brief-stakeholders is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 564 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.