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 verbalgit 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/verbal)<a href="https://agentmods.dev/skills/bromso/metapowers/verbal"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/verbal.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.00549 |
| Opus 5 | $0.00006 | $0.00275 |
| Sonnet 5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
verbal 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verbal Identity
Develop the verbal identity for "$ARGUMENTS". Create the voice, tone, messaging framework, and language guidelines that bring the brand personality to life in words.
Prerequisites
Read .metapowers/branding/$ARGUMENTS/01-discover.md and .metapowers/branding/$ARGUMENTS/02-strategy.md. If 02-strategy.md does not exist, tell the user:
Phase 2 (Strategy) has not been completed for "$ARGUMENTS". Run
/branding:strategy $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 audience insights - Read
.metapowers/branding/$ARGUMENTS/02-strategy.mdfor personality, values, and positioning
- Read
-
Define brand voice:
- Voice is consistent — it's WHO the brand is
- Describe the voice using the personality traits from Strategy
- Provide "We are / We are not" examples
- Example: "We are confident but not arrogant. We are friendly but not casual."
-
Define tone variations:
- Tone adapts to context — it's HOW the brand speaks in different situations
- Define tone for: marketing, support, social media, formal communications, error messages
- For each context: tone description + example copy
-
Create messaging pillars:
- 3-5 key messages the brand consistently communicates
- For each pillar: headline, supporting statement, proof point
-
Develop tagline/endline options:
- Generate 3-5 tagline candidates
- Evaluate each against the positioning and personality
- Recommend the strongest option
-
Language guidelines:
- Preferred vocabulary and phrases
- Words and phrases to avoid
- Grammar and style preferences (e.g., Oxford comma, contractions, capitalization)
-
Write the artifact to
.metapowers/branding/$ARGUMENTS/03-verbal.md
Output
The verbal identity written to .metapowers/branding/$ARGUMENTS/03-verbal.md. Present a summary to the user highlighting:
- Voice description in one sentence
- Top tagline recommendation
- Messaging pillars overview
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.
- 6d ago First seen · 56 lines · 12 tokens per session scan A 9f5979bd9a01
verbal 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 549 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.
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.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.