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-makegit 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.00033 | $0.00451 |
| Opus 5 | $0.00016 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
brand-make 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-make
The hero command. Turn a plain-language request into a finished, on-brand asset.
Steps
- Resolve the active brand. Read
brand/.active(or the singlebrand/dir) vialib/brand.mjs→resolveActive. If none exists, tell the user to run/brand-newand stop. - Load + validate the profile with
loadProfile/validateProfile. If validation fails, report the offending field and stop. - Route by asset type (rule of thumb: text/geometry → vector; photographic →
raster, which is opt-in):
- logo / wordmark / monogram / favicon → generate-logo skill.
- social post / story / banner / OG card / thumbnail → generate-social skill.
- letterhead / slide / one-pager → generate-doc-template skill.
- hero image / ad creative / background / texture / photo → generate-graphic
skill (opt-in raster: needs
BRAND_FORGE_RASTER=1+ an API key; if unset, say so and offer a vector alternative).
- Consider
art-directorfor anything ambiguous or multi-asset — have it propose the asset set and composition before generating. - Generate by calling the routed skill, writing files under
output/(SVG for vector assets; PNG for raster graphics, optionally with an SVG overlay). - Enforce with the
visual-guardiansubagent (palette, contrast, clear-space, type). Apply fixes or surface flags. - Report the saved paths and show a short preview/description of each asset.
Never auto-post or upload. Output is local files the user reviews.
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 · 35 lines · 33 tokens per session scan A f8479f83bc8d
brand-make is a command published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 451 once invoked, about $0.0002 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.