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/jgerton/brand-toolkit/brand-syncgit clone --depth 1 https://github.com/jgerton/brand-toolkitWrote 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/jgerton/brand-toolkit/brand-sync)<a href="https://agentmods.dev/commands/jgerton/brand-toolkit/brand-sync"><img src="https://agentmods.dev/badge/commands/jgerton/brand-toolkit/brand-sync.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 | $0.00031 | $0.00657 |
| Opus 5 | $0.00015 | $0.00329 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
brand-sync 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Sync
Synchronize brand-brief.md between the current project directory and an external vault location.
The vault can be anything: an Obsidian vault, a plain directory, a shared drive. The path is configured per-project via the vault_path field in your brand-brief.md.
Process
1. Locate Files
Find brand-brief.md in both locations:
- Project: Current working directory or codebase path from the brief
- Vault: Read
vault_pathfrom the brand brief's YAML frontmatter
If vault_path is not set, ask the user where they want to sync to. Use the project field from the YAML frontmatter to suggest a filename (e.g., {project}.md).
2. Conflict Detection
If both files exist, compare last_updated timestamps:
- Project is newer: Offer to push project → vault
- Vault is newer: Offer to pull vault → project
- Same timestamp: No sync needed
- Both modified since last sync: Conflict. Present both versions' key differences and ask user which to keep, or offer to merge.
3. Sync Actions
Push (project → vault):
- Read project brand-brief.md
- Copy to vault path, creating the brands/ directory if needed
- Update vault_path in the project copy
- Confirm: "Pushed brand-brief.md to vault at [path]"
Pull (vault → project):
- Read vault brand file
- Copy to project directory as brand-brief.md
- Update codebase path in the brief if different
- Confirm: "Pulled brand-brief.md from vault at [path]"
Create vault entry (vault doesn't exist yet):
- Read project brand-brief.md
- Ask user for vault path if
vault_pathis not set - Create vault file at the configured path as
{project}.md - If the vault is an Obsidian vault (detected by
.obsidian/directory), add Obsidian-compatible frontmatter (tags, aliases) - Update vault_path in project copy
- Confirm: "Created vault entry at [path]"
4. Vault Formatting
When creating or updating the vault copy:
- Preserve all brand-brief YAML fields
- Keep the markdown body intact
- If Obsidian vault detected (
.obsidian/directory exists in vault root):- Add
tags: [brand, {business_type}] - Add
aliases: [{brand_name}]if brand_name is set
- Add
- Otherwise: Plain markdown, no extra frontmatter
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.
- 4d ago First seen · 74 lines · 31 tokens per session scan A 1f690f5347b4
brand-sync is a command published in the GitHub repository jgerton/brand-toolkit (59 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 657 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-30.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.