Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add andisab/swe-marketplace/plugin install knowledgewareWrote 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/andisab/swe-marketplace/brandware)<a href="https://agentmods.dev/skills/andisab/swe-marketplace/brandware"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/brandware/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/andisab/swe-marketplace/brandware"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/brandware.svg" alt="Reviewed on agentmods" width="80" 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.00210 | $0.02952 |
| Opus 5.5 | $0.00084 | $0.01181 |
| Sonnet 5.5 | $0.00042 | $0.00590 |
| Haiku 4.5 | $0.00021 | $0.00295 |
Grade B, and why
brandware scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
5. **Prefer the user directory when it exists.** Anything inside the plugin install (`styles/brands/`) is wiped by plugin updates. When `KNOWLEDGEWARE_BRANDS_DIR` is set, write new brandbooks, token caches, assets, and t How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brandware — Brand & Style Registry
One registry, many consumers. Brandbooks live here once; slideware decks, knowledgebase sites, and chartware diagrams all render from the same visual identity.
Plugin root: ${CLAUDE_PLUGIN_ROOT} — two directories above this skill's folder (../../ from here). All paths below are relative to it.
Layout
styles/ # the registry (plugin root)
├── *.md # 5 default generic styles (style-1..style-5) — marketplace-safe
├── tokens/ # derived JSON token caches for defaults
└── brands/ # brandbooks — brand-specific / proprietary (NOT in the plugin repo,
│ # except the checked-in acmecorp example)
├── DEFAULT # optional one-line marker: the registry name to use when no style is named
├── <name>.md # canonical brandbook — THE source of truth per brand
├── tokens/<name>.json # derived token cache (regenerable; never hand-edit)
└── <name>/assets/ # per-brand assets: logo-light.svg, wordmark.png, ... (never mixed across brands)
$KNOWLEDGEWARE_BRANDS_DIR/ # OPTIONAL user-owned brands directory — same layout as styles/brands/
│ # (DEFAULT marker, <name>.md, tokens/, <name>/assets/). Lives anywhere
│ # the user chooses, so it SURVIVES plugin updates. Entries here shadow
│ # plugin entries on name collision; its DEFAULT marker wins too.
scripts/ # shared tooling (plugin root)
├── load-style.js # style/brandbook → tokens (with cache)
├── list-styles.js # discover what's installed
├── derive-style.js # live website → brandbook .md (heuristic)
├── install-fonts.sh # install a brand's Google Fonts locally (see §Fonts)
└── fetch-resource.sh # Google Drive URL → local file
skills/brandware/references/
├── brandbook-spec.md # the .md format every style/brandbook follows (prose layer + optional frontmatter)
├── consumer-mappings.md # how each consumer skill maps tokens onto its medium
└── chart-styling.md # how to style data charts (bar/line/pie/KPI) from a brandbook
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 132 lines · 210 tokens per session scan B 62b8beea0afd
brandware is a skill published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed today), licensed MIT. It adds 210 tokens to every session and 2,952 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-17.
Other skills, from other repositories
ccc-brainstorm
Design-first ideation gate: three parallel agents propose a simple, a scalable and a user-delight approach, rendered as a tradeoff matrix, then you pick a direction. No code is written. Use when the user asks how to build X, which approach to take, is torn between options, or types $ccc-brainstorm.
matilha-design
Use when user is making UX, UI, or visual-design decisions in any phase — guides via core design heuristics and delegates to matilha-design-pack or matilha-ux-pack if installed.
accessibility-compliance-accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
ux-design
Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.