build

build is a command for Claude Code from searchbrat/marketing-intelligence-layer. It costs 35 tokens per session (3,337 once invoked), scanned A, original, MIT.

A command for building or updating a marketing intelligence layer from notes and files. It can read a local raw folder or a Google Drive folder, then add new findings to an existing layer or create one from scratch.

In plain words
What is it for?
Use /build for local files, /build drive for notes in Google Drive, and /build setup to change the configuration. It is intended for organizing information about areas such as demand generation, advertising, SEO, content, measurement, onboarding, and leadership.
Why use it?
It removes the manual work of turning scattered marketing notes into a reusable reference. It also provides setup for the user's name, role, and topics before building.

Command for Claude Code

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 commands/searchbrat/marketing-intelligence-layer/build
Clone the repo
git clone --depth 1 https://github.com/searchbrat/marketing-intelligence-layer

Made for: Claude Code.

Wrote 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.

agentmods badge for build

README.md
[![agentmods](https://agentmods.dev/badge/commands/searchbrat/marketing-intelligence-layer/build.svg)](https://agentmods.dev/commands/searchbrat/marketing-intelligence-layer/build)
Your own site
<a href="https://agentmods.dev/commands/searchbrat/marketing-intelligence-layer/build"><img src="https://agentmods.dev/badge/commands/searchbrat/marketing-intelligence-layer/build.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,337 The whole file, excluding the scripts and references it only reads on demand.
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.00035 $0.03337
Opus 5 $0.00017 $0.01669
Sonnet 5 $0.00007 $0.00667
Haiku 4.5 $0.00003 $0.00334

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

Security

Grade A, and why

build 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.

.claude/commands/build.md · 291 lines

How it starts

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

/build — Marketing Intelligence Layer Builder

Three modes:

  • /build — read notes from the local raw/ folder
  • /build drive — read notes from a Google Drive folder
  • /build setup — change your name, role, or topics (re-runs the setup questions)

Step 0: Get ready

Is this the first time?

Local mode: Look for index.html in the project root. Drive mode: Look for index.html in the Drive root folder.

  • If it exists, this is an update — new learnings will be added to the existing intelligence layer.
  • If it doesn't exist, this is a first build — a fresh intelligence layer will be created.

First-time setup

If config.json doesn't exist yet, walk the user through setup before doing anything else:

"Before we start, I need a few things:"

1. Name and role:

"1. Your name — this goes at the top of your intelligence layer 2. Your role — e.g. 'VP Marketing', 'Head of Growth', 'CMO'"

2. Custom topics:

"Your intelligence layer comes with 8 default topics: Demand Generation, Paid Advertising, SEO, Content Marketing, Attribution & Measurement, Product Marketing, Activation & Onboarding, and Leadership & Strategy.

Want to add any of your own? For example, 'AI in Marketing', 'Brand', 'Partnerships', 'Community'. Just list them — you can always add more later by running /build setup."

If the user provides custom topics, ask for a one-line description of each so the routing logic knows what belongs there.

Save everything to config.json:

{
  "user_name": "Jane Smith",
  "user_role": "VP Marketing",
  "custom_topics": [
    {"id": "ai-marketing", "name": "AI in Marketing", "description": "Using AI tools and agents in marketing workflows, AI strategy, prompt engineering for marketers"},
    {"id": "partnerships", "name": "Partnerships", "description": "Partner programs, co-marketing, channel partnerships, affiliate strategy"}
  ]
}

If they don't want custom topics, leave custom_topics as an empty array.

Read the full file on GitHub · 291 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. 4d ago First seen · 291 lines · 35 tokens per session scan A bcf1f9d9f6f1

Subscribe to this mod's changes

build is a command published in the GitHub repository searchbrat/marketing-intelligence-layer (25 stars, last pushed 23d ago), licensed MIT. It adds 35 tokens to every session and 3,337 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.