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.00535 |
| Opus 5.5 | $0.00013 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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 22d 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 — 59 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 change their stance.
- 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 changes their stance |
|---|---|---|---|---|
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.
- 22d ago Changed · +6 lines ea3fea1bf883
- 23d ago Changed · -4 lines 9cc812e1f246
- 24d ago Changed 399bf4b419f1
- 1mo ago First seen · 57 lines · 33 tokens per session scan A 00a095cf2a5a
brief-stakeholders is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 535 once invoked, about $0.0001 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
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.