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 britt/agent-skills --skill stakeholder-trackinggit clone --depth 1 https://github.com/britt/agent-skillsWrote 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/britt/agent-skills/stakeholder-tracking)<a href="https://agentmods.dev/skills/britt/agent-skills/stakeholder-tracking"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/stakeholder-tracking.svg" alt="Measured on agentmods" 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.00058 | $0.00989 |
| Opus 5 | $0.00029 | $0.00495 |
| Sonnet 5 | $0.00012 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
stakeholder-tracking 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Tracking
Purpose
Help users define stakeholder personas and track their goals, ensuring all perspectives are addressed throughout the project lifecycle.
When to Use This Skill
- Starting a new project and need to identify stakeholders
- Plus any of the triggers in the Natural Language Triggers table below
Storage Format
Each stakeholder is a markdown file at docs/stakeholders/<name>.md containing a YAML block. List stakeholders with Glob over docs/stakeholders/*.md; search profile contents (a goal, role, or issue number) with Grep over that directory.
type: stakeholder
name: End User
role: Product manager
description: Plans features and writes specs for the engineering team
goals:
- Quickly create well-formed issues
- AI assistance for gap analysis
painPoints:
- Writing specs is time-consuming
- Context switching between tools
priorities:
- Context
- Quality
- Integration
linkedIssues:
- goal: "Quickly create well-formed issues"
issues: [42, 56]
Workflow
Managing Profiles
To add a stakeholder, ask conversationally for their name, role, description, goals (what they want to achieve), pain points (current frustrations), and priorities (in order); confirm the profile, then write it to docs/stakeholders/<name>.md in the YAML format above. To list, Glob the directory and present a summary table of name, role, and top goals. To view, update, or remove a stakeholder, Read their file and present it, apply the requested edits, or delete it (confirm before deleting).
Linking Issues to Goals
When an issue addresses a stakeholder goal:
- Read the stakeholder's file in
docs/stakeholders/ - Add the issue number to the
linkedIssuessection under the matching goal - Save the updated file
Checking Coverage
When asked about stakeholder coverage:
- Read all profiles in
docs/stakeholders/ - Fetch open issues with
gh issue list --state open --json number,title(requires the gh CLI) - For each stakeholder, check which goals have linked issues and which don't
- Calculate coverage percentages
- Present a coverage report highlighting gaps
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.
- 7d ago First seen · 114 lines · 58 tokens per session scan A d06768c66e02
stakeholder-tracking is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 989 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.