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 commands/localplugins/plugins/brand-exportgit clone --depth 1 https://github.com/localplugins/pluginsWhat 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.00029 | $0.00490 |
| Opus 5 | $0.00015 | $0.00245 |
| Sonnet 5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
brand-export 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 yesterday.
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
/brand-export
Rasterize a vector asset to PNG on demand. brand-forge ships SVG (scalable, editable, zero-permission); PNG copies are produced here when you need them. No PNGs are stored in the repo.
Steps
-
Pick the source SVG from
output/(ask if not given) and a target width (default 1024). -
Try the built-in rasterizer:
node "${CLAUDE_PLUGIN_ROOT}/lib/rasterize.mjs" output/<name>.svg output/<name>.png <width>This uses the optional
sharpdependency. If it prints a "needs sharp" message,sharpisn't installed — eithernpm i sharpin the plugin, or use an OS tool below.
OS-native fallbacks (no dependency)
- macOS (Quick Look):
qlmanage -t -s <width> -o <output-dir> output/<name>.svg # writes <name>.svg.png - Headless Chrome/Chromium (wrap the SVG so it fills the viewport, then screenshot):
printf '<!doctype html><style>html,body{margin:0}svg{width:100vw;height:100vh}</style>%s' "$(cat output/<name>.svg)" > /tmp/w.html "chrome" --headless=new --disable-gpu --force-device-scale-factor=2 \ --screenshot=output/<name>.png --window-size=<w>,<h> file:///tmp/w.html - librsvg:
rsvg-convert -w <width> output/<name>.svg -o output/<name>.png
Notes
- Prefer keeping the SVG as the source of truth; export PNG for platforms that need raster.
- Fonts render with whatever is installed on the machine doing the rasterization; if a brand font is missing, the declared fallback applies (flag the substitution).
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.
- yesterday First seen · 46 lines · 29 tokens per session scan A 28180c6ab2ec
brand-export is a command published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 490 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 commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.