Borrowing it
Nothing to install: this file belongs to FunnelEnvy/marketing-clis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FunnelEnvy/marketing-clis/master/CLAUDE.mdgit clone --depth 1 https://github.com/FunnelEnvy/marketing-clisWrote 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/funnelenvy/marketing-clis/claude-md)<a href="https://agentmods.dev/instructions/funnelenvy/marketing-clis/claude-md"><img src="https://agentmods.dev/badge/instructions/funnelenvy/marketing-clis/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.
<a href="https://agentmods.dev/instructions/funnelenvy/marketing-clis/claude-md"><img src="https://agentmods.dev/badge/instructions/funnelenvy/marketing-clis/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.03790 | $0.03790 |
| Opus 5 | $0.01895 | $0.01895 |
| Sonnet 5 | $0.00758 | $0.00758 |
| Haiku 4.5 | $0.00379 | $0.00379 |
Grade A, and why
marketing-clis 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 10d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing CLIs — Meta Repository
Project Vision
This is a meta-repository that orchestrates the creation and maintenance of open source CLI tools for marketing platforms that lack them. Each marketing tool gets its own standalone GitHub repo for discoverability (easier to find via search), with cross-references back to this meta-repo. This repo contains:
- Registry — index of all generated CLIs with status, links, and metadata
- Generator skill —
/generate-cliClaude Code skill that creates new CLI repos from API documentation - Shared libraries — common auth, output formatting, config, and rate limiting patterns
- Templates — repo scaffolding, CI/CD, docs, and release automation
All CLIs are Node.js (TypeScript) with single-binary distribution. Everything is MIT licensed.
Agent Teams Strategy
This project is designed for Claude Code agent teams. The architecture naturally avoids file conflicts because each CLI is a separate repo in a sibling directory.
Recommended workflow:
- Lead agent builds the meta-repo foundation (shared packages, template, generator skill) — this is sequential and must complete first
- Lead agent spawns 5 teammates, one per CLI — each teammate owns an entire standalone repo directory and works independently
- Lead agent monitors progress, synthesizes results, updates the meta-repo registry and README when teammates finish
Why this works well for agent teams:
- Zero file conflict risk — each teammate writes to its own
clis/{tool}-cli/directory - Each CLI is fully independent — no cross-teammate dependencies after shared packages are built
- Teammates can research APIs in parallel (the slowest part of CLI generation)
- Lead only needs to update
registry.jsonandREADME.mdin the meta-repo at the end
Teammate spawn guidelines:
- Each teammate prompt must include: tool name, API docs URL, auth method, priority endpoints, and the full path to create the repo
- Each teammate prompt must reference this CLAUDE.md for standards
- Teammates should be told NOT to modify anything in the meta-repo — only the lead does that
- Teammates should be told to use the shared packages from
shared/as reference for patterns but to bundle/copy the code into their own repo
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.
- 10d ago First seen · 339 lines · 3,790 tokens per session scan A 9cd0064e360f
marketing-clis CLAUDE.md is an instructions file published in the GitHub repository FunnelEnvy/marketing-clis (11 stars, last pushed 6mo ago), licensed MIT. It adds 3,790 tokens to every session, about $0.0190 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).
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.