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/discovernpx skills add bromso/metapowers --skill discovergit 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/discover)<a href="https://agentmods.dev/skills/bromso/metapowers/discover"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/discover.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.00012 | $0.00448 |
| Opus 5 | $0.00006 | $0.00224 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
discover 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
Discover
Research the brand landscape for "$ARGUMENTS". Gather insights about the business, audience, competitors, and market to inform brand strategy.
Prerequisites
None — this is the first phase.
Process
-
Ask the user key discovery questions:
- What does the business do? What problem does it solve?
- Who is the target audience? (demographics, psychographics)
- Who are the main competitors?
- What makes this business different?
- Are there existing brand elements to audit? (logo, colors, messaging)
- What is the brand's aspiration? Where should it be in 3-5 years?
-
If existing brand assets exist:
- Ask the user to place assets in
.metapowers/branding/$ARGUMENTS/assets/(logo/, fonts/, imagery/) - Review and document what exists
- Assess current brand strengths and weaknesses
- Ask the user to place assets in
-
Competitive brand analysis:
- Use WebSearch to research competitor brands
- Document their positioning, visual identity, and messaging
- Identify gaps and opportunities for differentiation
-
Audience research:
- Use WebSearch to understand the target audience's preferences, behaviors, and expectations
- Document audience personas with needs and pain points
-
Write the artifact to
.metapowers/branding/$ARGUMENTS/01-discover.mdwith sections:- Business Overview — what the business does, its goals
- Existing Brand Audit — current assets, strengths, weaknesses (if applicable)
- Competitive Landscape — competitor brand analysis
- Target Audience — personas, needs, expectations
- Market Insights — trends, opportunities, gaps
- Key Takeaways — most important findings for the Strategy phase
Output
The discovery brief written to .metapowers/branding/$ARGUMENTS/01-discover.md. Present a summary to the user highlighting:
- Key audience insights
- Competitive positioning gaps
- Biggest brand opportunity identified
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 · 51 lines · 12 tokens per session scan A 58107de571fd
discover is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 448 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.