Borrowing it
Nothing to install: this file belongs to imaginpro/imaginepro-claude-plugin. 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/imaginpro/imaginepro-claude-plugin/main/CLAUDE.mdgit clone --depth 1 https://github.com/imaginpro/imaginepro-claude-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/imaginpro/imaginepro-claude-plugin/claude-md)<a href="https://agentmods.dev/instructions/imaginpro/imaginepro-claude-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/imaginpro/imaginepro-claude-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.1 | $0.02414 | $0.02414 |
| Opus 5 | $0.01207 | $0.01207 |
| Sonnet 5 | $0.00483 | $0.00483 |
| Haiku 4.5 | $0.00241 | $0.00241 |
Grade A, and why
imaginepro-claude-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 7d 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 — 324 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.
Project Overview
This is the ImaginePro Claude Code Plugin - a pure documentation/specification plugin that wraps the ImaginePro MCP server with specialized agents, slash commands, and workflows for professional AI image and video generation within Claude Code.
Critical Architecture Understanding:
- This plugin contains NO implementation code - it's pure markdown/JSON
- The actual functionality comes from
imaginepro-mcp-server(npm package) - The plugin provides UX layer: agents, commands, documentation, workflows
- The MCP server provides infrastructure: 8 MCP tools for image/video generation
Repository Structure
imaginepro-claude-plugin/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest - defines metadata, features, requirements
├── .mcp.json # MCP server config - references imaginepro-mcp-server via npx
├── agents/ # 4 specialized agent specifications (markdown)
│ ├── web-asset-producer.md # Web development assets
│ ├── ui-asset-generator.md # UI/UX design assets
│ ├── marketing-creative.md # Marketing materials
│ └── directory.md # Video workflows
├── commands/ # 5 slash command specifications (markdown)
│ ├── imagine-pro.md # Intelligent generation with guidance
│ ├── upscale-it.md # Production quality enhancement
│ ├── vary-it.md # Smart variations
│ ├── video-flow.md # Video workflow automation
│ └── imagine-guide.md # Interactive learning
├── docs/ # User documentation
│ ├── quick-start.md
│ ├── troubleshooting.md
│ ├── workflows/ # Complete workflow guides
│ └── prompt-library/ # Curated prompt examples
└── examples/ # Real-world project walkthroughs
Plugin Architecture
How It Works
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.
- 7d ago First seen · 324 lines · 2,414 tokens per session scan A 64c82b6a144f
imaginepro-claude-plugin CLAUDE.md is an instructions file published in the GitHub repository imaginpro/imaginepro-claude-plugin (5 stars, last pushed 10mo ago), licensed MIT. It adds 2,414 tokens to every session, about $0.0121 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
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).
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.
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).
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.