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/visualnpx skills add bromso/metapowers --skill visualgit clone --depth 1 https://github.com/bromso/metapowersWhat 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.00014 | $0.00643 |
| Opus 5 | $0.00007 | $0.00321 |
| Sonnet 5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
visual 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 2d 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.
Visual Identity
Define the visual identity system for "$ARGUMENTS". Create specifications for logo usage, color palette, typography, and imagery that express the brand visually.
Prerequisites
Read .metapowers/branding/$ARGUMENTS/02-strategy.md and .metapowers/branding/$ARGUMENTS/03-verbal.md. If 03-verbal.md does not exist, tell the user:
Phase 3 (Verbal) has not been completed for "$ARGUMENTS". Run
/branding:verbal $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/02-strategy.mdfor personality and positioning - Read
.metapowers/branding/$ARGUMENTS/03-verbal.mdfor voice and tone
- Read
-
If the user has existing assets:
- Review logo files in
.metapowers/branding/$ARGUMENTS/assets/logo/ - Review fonts in
.metapowers/branding/$ARGUMENTS/assets/fonts/ - Review imagery in
.metapowers/branding/$ARGUMENTS/assets/imagery/ - Document and formalize what exists
- Review logo files in
-
If creating from scratch, define:
Logo usage rules:
- Minimum size, clear space requirements
- Approved variations (primary, icon, monochrome, reversed)
- Prohibited uses
- Ask the user to provide/create logo files and place in
.metapowers/branding/$ARGUMENTS/assets/logo/
Color palette:
- Primary colors (2-3) with hex, RGB values
- Secondary colors (2-4) with hex, RGB values
- Neutral colors for backgrounds and text
- Accessibility: contrast ratios for text on each background
Typography:
- Primary typeface: name, weights, usage (headings vs. body)
- Secondary typeface (if needed)
- Type scale: sizes, weights, line heights for each level
- Ask the user to provide font files and place in
.metapowers/branding/$ARGUMENTS/assets/fonts/
Imagery style:
- Photography style (mood, composition, subjects)
- Illustration style (if applicable)
- Icon style
- Do's and don'ts
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.
- 2d ago First seen · 64 lines · 14 tokens per session scan A 71f44b3a5e5c
visual is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 643 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
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
change
Track and inspect graph changes, diffs, temporal updates, and the impact of new data on Semantica knowledge graphs.
coding
编写并运行 Python 代码，验证脚本逻辑和输出。.