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 shajith003/awesome-claude-skills --skill brand-guidelinesgit clone --depth 1 https://github.com/shajith003/awesome-claude-skillsWrote 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/shajith003/awesome-claude-skills/brand-guidelines)<a href="https://agentmods.dev/skills/shajith003/awesome-claude-skills/brand-guidelines"><img src="https://agentmods.dev/badge/skills/shajith003/awesome-claude-skills/brand-guidelines/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/shajith003/awesome-claude-skills/brand-guidelines"><img src="https://agentmods.dev/badge/skills/shajith003/awesome-claude-skills/brand-guidelines.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.00050 | $0.00518 |
| Opus 5 | $0.00025 | $0.00259 |
| Sonnet 5 | $0.00010 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
brand-guidelines 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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
1 file 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.
- 12d ago First seen · 74 lines · 50 tokens per session scan A 1120b3769e29
brand-guidelines is a skill published in the GitHub repository shajith003/awesome-claude-skills (25 stars, last pushed yesterday), with no licence file. It adds 50 tokens to every session and 518 once invoked, about $0.0003 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-30.
Other skills, from other repositories
code-quality-principles
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.
methodology-curator
Surface expert frameworks. Use when creating or evaluating skills, hooks, or agents.
design
Elicit the project's design north-star + design-system reference (the two artifacts the consumed design audits read at runtime); no agent copies are authored. Derived from the project's actual UI surfaces, the user's named design benchmarks, and past design failure modes. Invoke /dotclaude:design in any project root…
iterative-polish-autoloop
Drive a multi-screen flow from raw to award-quality through a bounded iterative loop — reset to a clean fixture, capture every state, grade across three scrutiny layers (reviewer agent + composition scan + backend-truth probe), apply ONE highest-ROI fix, commit atomically, re-run — until award-quality OR a hard…
element-reuse
Before reusing an existing string, component, or copy pattern on a NEW surface — locate its current usage with grep, classify both the existing and the proposed surface by type, and apply the verdict matrix. Catches first-touch copy leaking onto a daily-driver surface, a bug invisible to lint, code review, and…
journey-mapping
Build the prior-surface inventory before designing OR auditing any screen — walk every surface the user touched before reaching this one, classify each by type, and apply the forbidden-pattern matrix so first-touch copy/voice/chrome never leaks onto a daily-driver surface. Load before any new design spec or any…