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/jasonstrimpel/lead-genius-plugin/claude-mdgit clone --depth 1 https://github.com/jasonstrimpel/lead-genius-pluginWrote 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/jasonstrimpel/lead-genius-plugin/claude-md)<a href="https://agentmods.dev/instructions/jasonstrimpel/lead-genius-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/jasonstrimpel/lead-genius-plugin/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.01330 | $0.01330 |
| Opus 5 | $0.00665 | $0.00665 |
| Sonnet 5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
lead-genius-plugin 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 — 69 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.
What This Is
A Claude Code plugin (v1.9.0) that provides the /lead-genius:run command — a 15-phase conversational lead generation pipeline. It interviews users about their offering/GTM strategy, dispatches sequential research agents to find companies and decision makers, then generates personalized outreach emails and marketing content (blog, LinkedIn posts, case study, sales deck scripts).
There is no build system, package manager, or test suite. The codebase is entirely markdown files: agent definitions, commands, and skills interpreted by the Claude Code plugin runtime.
Plugin Structure
.claude-plugin/plugin.json # Plugin manifest (name, version, tools)
commands/run.md # Main orchestrator — the /lead-genius:run command
agents/ # 12 specialized agent prompts (markdown + YAML frontmatter)
skills/executive-outreach/ # Email generation skill with SKILL.md + reference examples
Architecture
The orchestrator (commands/run.md) drives a 15-phase sequential pipeline. It never does research or writes output itself — it delegates everything to agents via the Task tool.
Phase flow: Setup → Collateral Analysis → GTM Interview → Synthesis → Scoring Rubrics → Company Research → Company Synthesis → DM Research → DM Enrichment (ZoomInfo) → DM Compilation → Outreach → Marketing Content → Deck Script Generation → Mail Merge Export → Completion
Coordination model: File-based and fully sequential. Each research stage runs as a single agent that writes one output file (companies.md, dm-research.md); downstream agents score, enrich, and rank without de-duplicating, because a single sequential pass never produces duplicate entries. No inter-agent messaging.
Output directory: ./{slug}/ at project root, where slug is URL-safe derived from the offering. Each phase writes to a specific subdirectory (e.g., company-research/, decision-makers/). The deck-scripter writes markdown deck scripts in marketing/.
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 · 69 lines · 1,330 tokens per session scan A d7cf659f445a
lead-genius-plugin CLAUDE.md is an instructions file published in the GitHub repository jasonstrimpel/lead-genius-plugin (10 stars, last pushed 1mo ago), licensed MIT. It adds 1,330 tokens to every session, about $0.0066 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-31.
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.