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/squadcodercom/squadcoder/brandnpx skills add squadcodercom/squadcoder --skill brandgit clone --depth 1 https://github.com/squadcodercom/squadcoderWhat 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.00088 | $0.00750 |
| Opus 5 | $0.00044 | $0.00375 |
| Sonnet 5 | $0.00018 | $0.00150 |
| Haiku 4.5 | $0.00009 | $0.00075 |
Grade A, and why
ckm: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 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.
This is a copy
86% identical to brand — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand
Brand identity, voice, messaging, asset management, and consistency frameworks.
When to Use
- Brand voice definition and content tone guidance
- Visual identity standards and style guide development
- Messaging framework creation
- Brand consistency review and audit
- Asset organization, naming, and approval
- Color palette management and typography specs
Quick Start
Inject brand context into prompts:
node scripts/inject-brand-context.cjs
node scripts/inject-brand-context.cjs --json
Validate an asset:
node scripts/validate-asset.cjs <asset-path>
Extract/compare colors:
node scripts/extract-colors.cjs --palette
node scripts/extract-colors.cjs <image-path>
Brand Sync Workflow
# 1. Edit docs/brand-guidelines.md (or use /brand update)
# 2. Sync to design tokens
node scripts/sync-brand-to-tokens.cjs
# 3. Verify
node scripts/inject-brand-context.cjs --json | head -20
Files synced:
docs/brand-guidelines.md→ Source of truthassets/design-tokens.json→ Token definitionsassets/design-tokens.css→ CSS variables
Subcommands
| Subcommand | Description | Reference |
|---|---|---|
update |
Update brand identity and sync to all design systems | references/update.md |
References
| Topic | File |
|---|---|
| Voice Framework | references/voice-framework.md |
| Visual Identity | references/visual-identity.md |
| Messaging | references/messaging-framework.md |
| Consistency | references/consistency-checklist.md |
| Guidelines Template | references/brand-guideline-template.md |
| Asset Organization | references/asset-organization.md |
| Color Management | references/color-palette-management.md |
| Typography | references/typography-specifications.md |
| Logo Usage | references/logo-usage-rules.md |
| Approval Checklist | references/approval-checklist.md |
Scripts
| Script | Purpose |
|---|---|
scripts/inject-brand-context.cjs |
Extract brand context for prompt injection |
scripts/sync-brand-to-tokens.cjs |
Sync brand-guidelines.md → design-tokens.json/css |
scripts/validate-asset.cjs |
Validate asset naming, size, format |
scripts/extract-colors.cjs |
Extract and compare colors against palette |
What ships with it
16 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.
- references/approval-checklist.md 4.1 KB
- references/asset-organization.md 5.0 KB
- references/brand-guideline-template.md 3.5 KB
- references/color-palette-management.md 4.2 KB
- references/consistency-checklist.md 1.9 KB
- references/logo-usage-rules.md 5.3 KB
- references/messaging-framework.md 1.7 KB
- references/typography-specifications.md 4.9 KB
- references/update.md 3.3 KB
- references/visual-identity.md 1.8 KB
- references/voice-framework.md 2.0 KB
- scripts/extract-colors.cjs 9.1 KB runs code
- scripts/inject-brand-context.cjs 9.5 KB runs code
- scripts/sync-brand-to-tokens.cjs 9.9 KB runs code
- scripts/validate-asset.cjs 9.9 KB runs code
- templates/brand-guidelines-starter.md 6.5 KB
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 · 98 lines · 88 tokens per session scan A fa88aae90e87
ckm:brand is a skill published in the GitHub repository squadcodercom/squadcoder (11 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 750 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to brand, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…