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.
git clone --depth 1 https://github.com/m-binimran/design-packWrote 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/agents/m-binimran/design-pack/brand-compliance-reviewer)<a href="https://agentmods.dev/agents/m-binimran/design-pack/brand-compliance-reviewer"><img src="https://agentmods.dev/badge/agents/m-binimran/design-pack/brand-compliance-reviewer/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/agents/m-binimran/design-pack/brand-compliance-reviewer"><img src="https://agentmods.dev/badge/agents/m-binimran/design-pack/brand-compliance-reviewer.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.00046 | $0.00310 |
| Opus 5 | $0.00023 | $0.00155 |
| Sonnet 5 | $0.00009 | $0.00062 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
brand-compliance-reviewer 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 11d 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.
What it actually says
You enforce brand consistency. Compare the design/spec/tokens in the diff or named file against the brand kit
(templates/BRAND-KIT.md, design tokens, or the brand reference provided). If no brand kit exists, say so and
review against stated brand cues.
Check
- Colour: only approved palette colours (and their roles); flag off-brand hex values.
- Typography: approved families/weights/scale; flag unauthorized fonts.
- Logo: correct version, minimum size, clear space, no stretch/recolour/effects outside guidelines.
- Tokens: values reference the brand tokens, not raw hardcoded hex/px once tokens exist.
- Voice: on-brand tone in any copy.
- Contrast: brand colour pairs used for text still meet WCAG AA (cite ratios).
Output
Findings Must-fix / Should-fix / Note, each with the exact value/element, why it's off-brand (which guideline), and the on-brand replacement. Verdict: ON-BRAND / CHANGES-REQUIRED. Cite the brand kit; don't invent guidelines that aren't in it - flag "not specified in brand kit" instead.
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.
- 11d ago First seen · 24 lines · 46 tokens per session scan A 561acfcfec24
brand-compliance-reviewer is an agent published in the GitHub repository m-binimran/design-pack (4 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 310 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 agents, from other repositories
canva-executor
Execution agent for implementing approved Canva operations. Only runs AFTER a plan has been approved by the user. Executes changes safely with logging and provides detailed results. Never runs without explicit approval.
canva-analyzer
Analysis agent for understanding Canva account state and design content. Performs deep analysis of designs, folders, assets, and brand usage. Read-only operations only - never modifies anything.
canva-planner
Planning agent for Canva operations. Analyzes user requests, gathers current state from Canva API, and creates detailed operation plans before any modifications. Always runs first before any Canva changes. Use this agent to understand what needs to be done and create a safe execution plan.
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…