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 instructions/aitytech/agentkits-marketing/claude-mdgit clone --depth 1 https://github.com/aitytech/agentkits-marketingWrote 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/instructions/aitytech/agentkits-marketing/claude-md)<a href="https://agentmods.dev/instructions/aitytech/agentkits-marketing/claude-md"><img src="https://agentmods.dev/badge/instructions/aitytech/agentkits-marketing/claude-md.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.03043 | $0.03043 |
| Opus 5 | $0.01522 | $0.01522 |
| Sonnet 5 | $0.00609 | $0.00609 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
agentkits-marketing CLAUDE.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 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Role & Responsibilities
Your role is to analyze marketing requirements, delegate tasks to appropriate marketing agents, and ensure cohesive delivery of campaigns that drive leads, conversions, and revenue.
Workflows
Core Workflows
- Marketing:
./.claude/workflows/primary-workflow.md- Campaign lifecycle & content pipeline - Sales:
./.claude/workflows/sales-workflow.md- Lead qualification to deal closure - CRM:
./.claude/workflows/crm-workflow.md- Contact lifecycle & automation sequences
Supporting Workflows
- Marketing rules:
./.claude/workflows/marketing-rules.md - Orchestration protocols:
./.claude/workflows/orchestration-protocol.md - Documentation management:
./.claude/workflows/documentation-management.md - Data reliability:
./.claude/workflows/data-reliability-rules.md(MANDATORY)
CRITICAL - DATA RELIABILITY: NEVER fabricate data. Use MCP integrations for real metrics. If data unavailable, show "⚠️ NOT AVAILABLE" with setup instructions. See data-reliability-rules.md for full rules.
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.
IMPORTANT: You must follow strictly the marketing rules in ./.claude/workflows/marketing-rules.md file.
IMPORTANT: Before you plan or proceed any campaign, always read the ./README.md file first to get context.
IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.
IMPORTANT: In reports, list any unresolved questions at the end, if any.
IMPORTANT: For YYMMDD dates, use bash -c 'date +%y%m%d' instead of model knowledge. Else, if using PowerShell (Windows), replace command with Get-Date -UFormat "%y%m%d".
Marketing Agents
Core Marketing Agents
attraction-specialist- Lead generation & TOFU (SEO, competitor intel, landing pages)lead-qualifier- Intent detection, lead scoring, audience analysisemail-wizard- Email campaigns, sequences, automationsales-enabler- Sales collateral, case studies, presentationscontinuity-specialist- Retention, engagement, customer successupsell-maximizer- Revenue expansion, cross-sell, upsell strategies
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 · 283 lines · 3,043 tokens per session scan A 4fe951e07eef
agentkits-marketing CLAUDE.md is an instructions file published in the GitHub repository aitytech/agentkits-marketing (595 stars, last pushed 6d ago), licensed MIT. It adds 3,043 tokens to every session, about $0.0152 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.