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 bromso/metapowers --skill stakeholder-needsgit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/stakeholder-needs)<a href="https://agentmods.dev/skills/bromso/metapowers/stakeholder-needs"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/stakeholder-needs/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/bromso/metapowers/stakeholder-needs"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/stakeholder-needs.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.00065 | $0.00823 |
| Opus 5.5 | $0.00026 | $0.00329 |
| Sonnet 5.5 | $0.00013 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
stakeholder-needs 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 3d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Legal Needs
Identify and map legal needs across all business units, products, and stakeholder groups for "$ARGUMENTS". Create a legal service catalog and prioritize support.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/legal/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
None — this is a Phase 0 Assess skill.
Process
-
Map business units and their legal touchpoints:
- Identify all business units, teams, and product lines
- For each, document current interactions with legal functions
- Note frequency and type of legal requests
-
For each business unit, assess:
- Contracts needed — vendor agreements, customer contracts, partner agreements, employment contracts, NDAs
- Compliance requirements — industry-specific regulations, data handling obligations, reporting duties
- IP considerations — patents, trademarks, copyrights, trade secrets, open source usage
- Regulatory exposure — which regulations directly affect this unit's operations
-
Create legal service catalog:
- List all legal services each group needs (contract review, compliance advice, IP filing, dispute resolution, etc.)
- Map current legal support coverage for each service
- Identify gaps where legal support is needed but not provided
-
Identify underserved areas:
- Business units operating without adequate legal support
- High-risk activities proceeding without legal review
- Teams using outdated templates or self-service legal documents
- Areas where legal bottlenecks slow business operations
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.
- 3d ago First seen · 64 lines · 65 tokens per session scan A 4af39293d265
stakeholder-needs is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 823 once invoked, about $0.0003 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-10-21.
Other skills, from other repositories
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
lead-orchestration
Use when you are the LEAD (main session) and an owner request arrives that needs agents -- intake, routing, briefs, follow-up, blocks, verification, learning, report. Canonical procedure from request to verified report; not for sub-agents executing a brief.
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
incident-management
Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes.…
schedule-development-and-analysis
Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited…