brandsystem-mcp AGENTS.md

A set of repository instructions for a server that extracts and manages a brand’s identity, including its logo, colors, typefaces, writing style, and visual rules. It stores the result as structured files, design tokens, and HTML reports.

In plain words
What is it for?
Developing or reviewing the brand-management server, generating brand files and reports, running its test suite, and submitting changes through a pull request.
Why use it?
It gives coding agents clear commands and contribution rules for building, testing, linting, and changing the server safely. The instructions also explain how changes reach the protected main branch.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/brandcode-studio/brandsystem-mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/Brandcode-Studio/brandsystem-mcp

Made for: Codex, OpenCode.

Per session 2,237 This file is loaded in full into every session.
When invoked 2,237 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02237 $0.02237
Opus 5 $0.01118 $0.01118
Sonnet 5 $0.00447 $0.00447
Haiku 4.5 $0.00224 $0.00224

Measured 2d ago against content hash 611835384dbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

brandsystem-mcp AGENTS.md 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

brandsystem-mcp

MCP server that extracts and manages brand identity (logo, colors, typography, voice, visual rules) for AI tools. Creates a .brand/ directory with structured YAML, DTCG tokens, and portable HTML reports.

Build and Test

npm install          # Install dependencies
npm run build        # Compile TypeScript to dist/
npm test             # Run vitest tests
npm run lint         # Type-check without emitting (tsc --noEmit)
npm run dev          # Watch mode for development
npm start            # Start the server (stdio transport)

Build must pass before committing. The entry point is src/index.ts (stdio transport) which creates the server from src/server.ts.

Branch and PR Workflow

main is protected by a ruleset (main-protection): no direct pushes, no force-pushes, PR required, and the CI matrix (build-and-test (20/22/24)) must pass before merge. Zero human approvals are required — CI is the gate. To land changes:

  1. Create a branch (feat/..., fix/...) and commit there
  2. Push and open a PR against main
  3. Enable auto-merge: gh pr merge --auto --squash — the PR lands when CI is green
  4. The branch is deleted automatically on merge

Do not attempt to push directly to main; the ruleset rejects it.

Architecture

src/
  index.ts         # Stdio transport entry point
  server.ts        # Creates McpServer, registers all 43 tools in priority order
  tools/           # One file per tool, mostly (41 files, 43 tools — brand-feedback.ts registers 3). Each exports a register(server) function.
                   # Counts drift; verify via `ls src/tools/*.ts | wc -l` and `grep -rc 'server\.tool(' src/tools/*.ts`
  lib/             # Shared utilities (brand-dir, css-parser, dtcg-compiler, content-scorer, etc.)
  types/           # TypeScript type definitions
  schemas/         # Zod schemas for validation
bin/
  brandsystem-mcp.mjs  # CLI entry point (npx @brandsystem/mcp)

Tool Registration Order (in server.ts)

Read the full file on GitHub · 195 lines

Changes

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.

  1. 2d ago First seen · 195 lines · 2,237 tokens per session scan A 611835384dbd

Subscribe to this mod's changes

brandsystem-mcp AGENTS.md is an instructions file published in the GitHub repository Brandcode-Studio/brandsystem-mcp (13 stars, last pushed 5d ago), licensed MIT. It adds 2,237 tokens to every session, about $0.0112 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.