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 skills add rfxlamia/pocketto --skill brand-designgit clone --depth 1 https://github.com/rfxlamia/pockettoWrote 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/rfxlamia/pocketto/brand-design)<a href="https://agentmods.dev/skills/rfxlamia/pocketto/brand-design"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/brand-design/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/rfxlamia/pocketto/brand-design"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/brand-design.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.00146 | $0.05053 |
| Opus 5.5 | $0.00058 | $0.02021 |
| Sonnet 5.5 | $0.00029 | $0.01011 |
| Haiku 4.5 | $0.00015 | $0.00505 |
Grade B, and why
brand-design 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat > .claude/hooks/session-start.sh <<'SCRIPT' How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Design
You are the Head of Brand. You turn vague brand language ("we want to feel trustworthy and modern") into a concrete, math-validated design system, then enforce it across the project — primarily via a project-scoped SessionStart hook, with a Claude rule file as fallback (see Step 7).
Core principle: Compute, never guess. Every color is derived by formula, every contrast ratio is calculated, every type size comes from a modular scale. "Feel" is the input; math is the output.
Violating the letter of this process — skipping a reference, eyeballing a color, writing the brief before the preview is confirmed — is violating the spirit of brand-design.
When to Use
Trigger this skill when:
- Starting a new project that needs a design system defined
- An existing design system needs refinement (color, type, tone, components)
- UI feels inconsistent with the intended brand identity
- An agent is about to build UI and there is no design authority to consult
Do NOT use for:
- Implementing a single component when
creative-brief.mdalready exists and needs no change → just read the brief and build - Regenerating framework tokens alone when the brief is unchanged — the token file is derived output; if only the wiring broke, re-run Step 8, not the whole skill
This is a standalone skill. It does not hand off to pocket-planning. Its deliverable is creative-brief.md + an enforcement rule, not a pipeline.
Mode Detection (Step 0 — do this first, every time)
Check: does docs/pocket/rule/creative-brief.md exist?
→ NO : DISCOVERY MODE → run Steps 1–7 in full
→ YES : REFINE MODE → jump to the Refine Mode Flow (bottom)
Before anything else, also scan the project to infer context: README, package.json,
existing CSS / tokens / theme files. This grounds the interview in reality instead of
asking the user things the repo already answers. Note whether the project has a CSS
surface (any .css file, <style> usage, or Tailwind dependency) — Step 8 gates on it.
What ships with it
7 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.
- 1mo ago First seen · 463 lines · 146 tokens per session scan B e76526d5abac
brand-design is a skill published in the GitHub repository rfxlamia/pocketto (6 stars, last pushed 9d ago), licensed MIT. It adds 146 tokens to every session and 5,053 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
fec-implement-from-design
A frontend implementation guide for turning designs or screenshots into reusable web pages and components.
fec-accessibility-check
A front-end accessibility review guide for checking whether websites and interfaces work for people with disabilities, including keyboard and screen-reader users. It uses WCAG 2.2 AA, a set of web accessibility guidelines, as its reference.
fec-storybook-component-doc
A workflow for documenting interface components in Storybook, a tool that displays UI components and their states in isolation. It covers stories, reusable setup wrappers, written documentation, interaction checks, accessibility checks, and visual baselines.
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
aesthetic-instrument
A committed aesthetic in the sense of skills/committed-aesthetic/SKILL.md: every rule below is checkable, and every value was read out of the source — packages/board/public/index.html and greatcto-site/styles.css — rather than chosen to write this document.
committed-aesthetic
How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when…