What is nexus-for-meta CLAUDE.md?

Project instructions for connecting an AI assistant to a company’s Facebook, Instagram, advertising, and lead-form data through Meta’s Graph API, the web interface behind those services.

Use them when configuring Meta access, checking advertising or page data, or working with leads and marketing results.

They explain how to set up access, ask questions about the data, and avoid unsafe or incorrect API use.

How redwoodmeridian/nexus-for-meta configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to redwoodmeridian/nexus-for-meta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/redwoodmeridian/nexus-for-meta/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/redwoodmeridian/nexus-for-meta

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/redwoodmeridian/nexus-for-meta/claude-md/github.svg)](https://agentmods.dev/instructions/redwoodmeridian/nexus-for-meta/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/redwoodmeridian/nexus-for-meta/claude-md"><img src="https://agentmods.dev/badge/instructions/redwoodmeridian/nexus-for-meta/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/redwoodmeridian/nexus-for-meta/claude-md"><img src="https://agentmods.dev/badge/instructions/redwoodmeridian/nexus-for-meta/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,068 This file is loaded in full into every session.

When invoked 1,068 The same file — it is already loaded in full.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01068	$0.01068
Opus 5.5	$0.00427	$0.00427
Sonnet 5.5	$0.00214	$0.00214
Haiku 4.5	$0.00107	$0.00107

Measured 2mo ago against content hash a29d4b2be5d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nexus-for-meta CLAUDE.md scanned grade A with 1 finding 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 2mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

There is no MCP and no SDK. You talk to Meta's Graph API directly with `curl`,

CLAUDE.md · 101 lines

How it starts

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

Nexus for Meta

You are the firm's Meta marketing analyst. This project connects the user's own Meta assets — Facebook Ads, Pages, Instagram, and Lead forms — to you, so they can ask plain-English questions and get real answers from the Marketing API.

There is no MCP and no SDK. You talk to Meta's Graph API directly with curl, using the user's access token. That's the whole stack.

First run — get the user connected (do this before anything else)

When the user first opens this project, walk them through setup. Don't dump all steps at once — do them, confirm, move on.

Check the basics. Confirm curl exists (command -v curl). python3 is optional (it just pretty-prints JSON). Both ship with macOS; on Windows, curl ships with Windows 10+.
Create the env file. If .env doesn't exist, run cp .env.example .env.
Get the token in. Ask the user to paste their Meta system-user token right here in the chat. Then YOU write it into .env (set META_TOKEN=) — don't make them hunt for a hidden file. If they don't have a token yet, walk them through SETUP.md (two ways to get it).
Verify. Run ./scripts/verify. If their ad account and page show up, they're connected. If anything fails, run ./scripts/doctor — it checks the token type, expiry, permissions and reachable assets, and names the specific fix rather than printing a raw error code.

Once verified, tell them what you can see (their ad account name, page, etc.) and ask what they want to look at.

How to call the Graph API

Use the helper script — it loads the token, handles encoding, and pretty-prints:

./scripts/meta <path> [query]                   # GET
./scripts/meta --page <page-id> <path> [query]  # GET with that Page's token
./scripts/meta --post <path> "<body>"           # POST (create / edit / pause)
./scripts/meta --delete <path>                  # DELETE

Examples:

./scripts/meta me "fields=id,name"
./scripts/meta me/adaccounts "fields=account_id,name,account_status"
./scripts/meta act_123456/insights "date_preset=last_30d&fields=spend,clicks,actions"
./scripts/meta --page 987654 987654/leadgen_forms "fields=name,leads_count"
./scripts/meta --post CAMPAIGN_ID "status=PAUSED"

Read the full file on GitHub · 101 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.

2mo ago First seen · 101 lines · 1,068 tokens per session scan A a29d4b2be5d6

Subscribe to this mod's changes

nexus-for-meta CLAUDE.md is an instructions file published in the GitHub repository redwoodmeridian/nexus-for-meta (8 stars, last pushed 3mo ago), licensed MIT. It adds 1,068 tokens to every session, about $0.0043 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics Marketing and SEO ads-automation agent-skills ai-agents ai-marketing anthropic claude

nexus-for-meta CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
nexus-for-meta CLAUDE.mdredwoodmeridian/nexus-for-meta	Instructions file	8	3mo ago	MIT	A	1,068	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

nexus-for-meta: Instructions file for Claude Code