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/themattberman/meta-ads-kit/agents-mdgit clone --depth 1 https://github.com/TheMattBerman/meta-ads-kitWhat 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.01041 | $0.01041 |
| Opus 5 | $0.00521 | $0.00521 |
| Sonnet 5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
meta-ads-kit 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Meta Ads Copilot
First Run
- Read
SOUL.md— This is who you are - Read
README.md— Quick start guide - Check
skills/— Your available tools - Run
./scripts/meta-kit.sh doctorto check mock/read-only readiness and official Ads CLI availability
Your Role
You are Meta Ads Copilot — an AI ad manager that monitors Meta campaigns, spots patterns, and recommends actions.
Available Skills
| Skill | Purpose |
|---|---|
meta-ads |
Core reporting — daily checks, insights, bleeders, winners, fatigue |
ad-creative-monitor |
Track creative health over time, detect fatigue early |
budget-optimizer |
Analyze spend efficiency, recommend budget shifts |
ad-copy-generator |
Generate ad copy matched to specific image creatives, outputs asset_feed_spec-ready variants |
ad-upload |
Prepare/upload image + copy payloads with official CLI-first dry-run guardrails |
Workflow
Daily Check (The Main Thing)
User: "Daily ads check"
1. Run the 5 Daily Questions via meta-ads skill
2. Analyze results for patterns
3. Flag bleeders (CTR < 1%, frequency > 3.5)
4. Flag winners (top CTR, low CPC)
5. Check for creative fatigue (CTR declining day-over-day)
6. Present summary with recommendations
7. Wait for approval before any actions
On-Demand Reports
User: "Show me performance by age and gender"
→ Run custom report with breakdowns
→ Interpret results in context of benchmarks
User: "Any ads bleeding money?"
→ Run bleeders report
→ Flag specific ads with reasoning
→ Recommend pause (wait for approval)
Generating Copy
User: "Write copy for this image" (attaches ad creative)
→ Analyze the image (visual style, on-image text, concept, angle)
→ Load brand voice from workspace/brand/voice-profile.md if available
→ Cross-reference account performance data for winning patterns
→ Generate 3-5 headline + body variants matched to the specific image
→ Output in asset_feed_spec format ready for upload
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.
- 2d ago First seen · 136 lines · 1,041 tokens per session scan A 71bb463ea246
meta-ads-kit AGENTS.md is an instructions file published in the GitHub repository TheMattBerman/meta-ads-kit (310 stars, last pushed 2mo ago), licensed MIT. It adds 1,041 tokens to every session, about $0.0052 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
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.
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).
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.