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 agentmods add skills/bromso/metapowers/strategynpx skills add bromso/metapowers --skill strategygit 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/strategy)<a href="https://agentmods.dev/skills/bromso/metapowers/strategy"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/strategy.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.00011 | $0.00495 |
| Opus 5 | $0.00005 | $0.00247 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
strategy 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 5d 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.
What it actually says
Strategy
Define the brand strategy for "$ARGUMENTS". Synthesize discovery findings into a clear positioning, values, personality, and differentiation framework.
Prerequisites
Read .metapowers/branding/$ARGUMENTS/01-discover.md. If this file does not exist, tell the user:
Phase 1 (Discover) has not been completed for "$ARGUMENTS". Run
/branding:discover $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/branding/$ARGUMENTS/skip-log.md.
Process
-
Read context files:
- Read
.metapowers/branding/$ARGUMENTS/01-discover.mdfor research findings - Read
plugins/branding/shared/brand-platform-template.mdfor output structure - Read
plugins/branding/shared/brand-prism-guide.mdfor the six brand facets
- Read
-
Define brand purpose, vision, and mission:
- Purpose: why does this brand exist?
- Vision: where is the brand going?
- Mission: what does it do, for whom, and how?
-
Define brand values:
- 3-5 core values that guide all brand decisions
- For each value: description and how it manifests in behavior
-
Craft positioning statement:
- For [target audience] who [need], [brand] is the [category] that [benefit] because [reason]
-
Define brand personality:
- 3-5 personality traits (e.g., bold, approachable, expert, playful)
- For each trait: how it influences communication
-
Map competitive differentiation:
- What sets this brand apart from each key competitor?
- The unique value proposition
-
Write the artifact to
.metapowers/branding/$ARGUMENTS/02-strategy.mdfollowing the brand platform template.
Output
The brand strategy written to .metapowers/branding/$ARGUMENTS/02-strategy.md. Present a summary to the user highlighting:
- The positioning statement
- Core values
- Key personality traits
- Primary differentiator
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.
- 5d ago First seen · 53 lines · 11 tokens per session scan A 3cda4545886d
strategy is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 495 once invoked, about $0.0001 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
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
laravel-billing
Use when implementing subscriptions, invoices, payment methods, webhooks, or billing portals with Laravel Cashier (Stripe or Paddle).
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.