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/tmj-90/gaffer/brandnpx skills add tmj-90/gaffer --skill brandgit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/brand)<a href="https://agentmods.dev/skills/tmj-90/gaffer/brand"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/brand.svg" alt="Measured on agentmods" 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.00102 | $0.01780 |
| Opus 5 | $0.00051 | $0.00890 |
| Sonnet 5 | $0.00020 | $0.00356 |
| Haiku 4.5 | $0.00010 | $0.00178 |
Grade A, and why
brand 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 5d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Establish or audit the brand
A factory that ships UI without a brand ships templates. This skill gives the product a deliberate, specific visual and verbal identity so everything built afterwards looks intentional. It either audits and extends an existing brand in its own idiom, or commits to one direction — never a vague "clean minimal" default that means nothing.
Run it two ways: as a delivery skill when a ticket asks for brand work (branch,
implement, evidence, submit like any other ticket), or as a lore seed when you want the
brand to govern future work — suggest_lore it so every later ticket inherits it.
This skill owns the identity (direction, palette, type pairing, voice). The structural
layer it feeds into — the three-tier token architecture and component state specs — lives in
the design-system pack; the visual execution of surfaces lives in frontend-design. Keep
SKILL.md lean and load the craft depth on demand:
| Topic | Reference |
|---|---|
Colour system (tiers, 60/30/10, oklch tokens, contrast) + typography (pairing, fluid scale) |
references/color-and-typography.md |
| Voice (spectrums, traits, do/don't), messaging hierarchy, consistency/approval checklist | references/voice-and-messaging.md |
Steps
- Consult and detect, in parallel. Call
search_lore(Memory MCP) for any existing brand, positioning, voice, or design ADRs. In the repo, look forBRAND.md,tokens.css, astyles/tokens.css, a.brand/dir, or a:rootblock of CSS custom properties. Decide: does a brand already exist? - If a brand exists → AUDIT and EXTEND in its idiom. Do not overwrite it with your
taste. Read its palette, type, and voice, then:
- Check it against the required-qualities bar below and name where it falls short.
- Fill gaps and add missing tokens in the existing direction (e.g. derive a hover/ focus state, a missing surface tier, a dark variant) — extend, don't replace.
- Record the audit findings and the additions in
BRAND.md.
- If no brand exists → COMMIT to one specific direction. Pick a real direction the
product actually wants and say why — editorial/magazine, neo-brutalism, glassmorphism
with real depth, light/dark luxury, bento, Swiss/International, retro-futurism. Never
"clean minimal", never default to dark mode reflexively. Then define all of:
- Palette as
oklchdesign tokens — surface, text, accent, plus semantic roles (success/warning/danger) and at least one depth/surface tier. Color used semantically, not one decorative accent on gray-on-white. (Tiers, 60/30/10, contrast →references/color-and-typography.md.) - Type pairing — a deliberate display + text pairing with a stated rationale and a
fluid scale (
clamp()tokens), not a default system stack used by accident. (Scale + loading →references/color-and-typography.md.) - Voice & positioning — who it's for, the one-line promise, and 3–5 voice
attributes with a do/don't example each. (Spectrums, traits, messaging hierarchy →
references/voice-and-messaging.md.) - Anti-template checklist — list which of the required qualities the brand delivers.
- Palette as
- Write the artifacts. Output a
BRAND.md(direction + rationale, palette, type, voice, checklist) and, when the work is visual, atokens.csssketch of the custom properties so delivery agents have something concrete to consume:
What ships with it
2 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.
- 5d ago First seen · 117 lines · 102 tokens per session scan A f53b6ffa2208
brand is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 102 tokens to every session and 1,780 once invoked, about $0.0005 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
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
security-best-practices
Security best practices and vulnerability prevention guidelines.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.
gh-pr-review
Review GitHub Pull Requests using the gh CLI. Use when a user asks to review a PR, perform code review, check a pull request, or provide feedback on proposed changes. Triggers on phrases like "review PR", "review pull request", "check PR", "code review".