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/guidelinesnpx skills add bromso/metapowers --skill guidelinesgit 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/guidelines)<a href="https://agentmods.dev/skills/bromso/metapowers/guidelines"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/guidelines.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 | $0.00010 | $0.00541 |
| Opus 5 | $0.00005 | $0.00270 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
guidelines 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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Guidelines
Compile all brand work for "$ARGUMENTS" into a comprehensive brand guidelines document — the single source of truth for anyone using the brand.
Prerequisites
Read all prior phase artifacts. If 04-visual.md does not exist, tell the user:
Phase 4 (Visual) has not been completed for "$ARGUMENTS". Run
/branding:visual $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 all prior artifacts:
- Read
.metapowers/branding/$ARGUMENTS/01-discover.mdfor context - Read
.metapowers/branding/$ARGUMENTS/02-strategy.mdfor brand platform - Read
.metapowers/branding/$ARGUMENTS/03-verbal.mdfor voice, tone, messaging - Read
.metapowers/branding/$ARGUMENTS/04-visual.mdfor visual identity - Read
plugins/branding/shared/brand-guidelines-template.mdfor output structure
- Read
-
Compile the brand guidelines following the template, combining:
- Brand overview (purpose, vision, mission, values from Strategy)
- Logo usage rules and variations (from Visual)
- Color palette with specifications (from Visual)
- Typography system (from Visual)
- Imagery and photography guidelines (from Visual)
- Voice and tone guidelines (from Verbal)
- Application examples — how the brand appears across key touchpoints
-
Add compliance rules:
- What must always be done (mandatory elements)
- What must never be done (prohibited uses)
- Common mistakes to avoid
- When to seek brand team approval
-
Reference assets:
- Link to all files in
.metapowers/branding/$ARGUMENTS/assets/ - List available logo variants, fonts, and imagery
- Link to all files in
-
Write the artifact to
.metapowers/branding/$ARGUMENTS/05-guidelines.md
Output
The brand guidelines written to .metapowers/branding/$ARGUMENTS/05-guidelines.md. Present a summary to the user highlighting:
- Sections covered
- Number of compliance rules
- Asset inventory
- How other domains can use these guidelines (e.g.,
/branding:audit)
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.
- 4d ago First seen · 54 lines · 10 tokens per session scan A 1bae8a950fc2
guidelines is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 541 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
frontend
Two-mode frontend skill: (1) authoring — accessibility, responsive layout, loading/error states, performance, DESIGN.md authoring, visual direction; (2) critique — READ-only scored review of built UI against anchored rubric, AI-slop detection, two isolated assessments. Router invokes mode via context.
design-android
Use when designing an Android screen or flow — deliverable is a device-framed HTML mockup and developer handoff spec, never Compose code.
design-ios
Use when designing an iOS or macOS screen or flow — deliverable is a device/window-framed HTML mockup and handoff spec, never SwiftUI code.
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-motion
Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.
design-review
Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup.