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 commands/anilcancakir/claude-code-plugins/my_brandgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWrote 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/commands/anilcancakir/claude-code-plugins/my_brand)<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugins/my_brand"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugins/my_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.00046 | $0.03728 |
| Opus 5 | $0.00023 | $0.01864 |
| Sonnet 5 | $0.00009 | $0.00746 |
| Haiku 4.5 | $0.00005 | $0.00373 |
Grade A, and why
my_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 — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/my_brand - Brand Identity Generator
Create comprehensive brand.md guidelines through an interactive workflow. This defines your brand's IDENTITY - not technical implementation.
Arguments
- No arguments: Full interactive workflow
--quick: Minimal brand (archetype + colors + fonts)--detect: Auto-detect from existing assets and enhance
Output: brand.md
A platform-agnostic brand identity document containing:
- Brand personality (archetype, values, attributes)
- Color palette (HEX values, not framework-specific)
- Typography (font names, scale ratios)
- Voice & tone guidelines
- Visual principles
This document works for ANY platform: web, mobile, print, marketing.
Workflow
Phase 1: Project Context
Check for project.md first:
# Check for project.md (should run /my_project first)
ls -la project.md PROJECT.md 2>/dev/null
# If exists, extract project identity
cat project.md 2>/dev/null | head -30
If project.md exists, use it for context:
- Project name for brand naming
- Target audience for tone calibration
- Problem/solution for brand positioning
If not:
NOTE: Consider running /my_project first to define your project identity.
This helps create more aligned brand guidelines.
Continue anyway?
1. Yes, proceed with brand creation
2. No, run /my_project first
Phase 2: Existing Brand Discovery
Search for existing brand elements:
# Find logo files
find . -name "logo.*" -o -name "icon.*" -o -name "favicon.*" 2>/dev/null | head -5
# Check for brand-related files
ls -la brand* BRAND* .brand/ design/ assets/ 2>/dev/null
# Extract colors from common config files
grep -h "primary\|secondary\|accent" tailwind.config.* theme.* colors.* 2>/dev/null | head -10
Present findings:
EXISTING BRAND ELEMENTS
=======================
Found:
- Logo: assets/logo.svg
- Colors detected: #3B82F6 (blue), #10B981 (green)
- No existing brand.md
Would you like to:
1. Build on existing elements
2. Start fresh
3. Extract and enhance current colors
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 · 517 lines · 46 tokens per session scan A 470cd6686138
my_brand is a command published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 46 tokens to every session and 3,728 once invoked, about $0.0002 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 commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
health
Run the Self-Star Doctor - a green/yellow/red health board across all 7 junctions of the self- loop.
plan-new
Plan a complex project with discovery, structure, and kill criteria.
remember
Explicitly save something to memory as an experience.
create-hook
Create a new custom automation hook.
review
Structured code review with severity categorization (distinct from Claude Code's PR review).