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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/imaginpro/imaginepro-claude-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/imaginpro/imaginepro-claude-plugin/agents-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/imaginpro/imaginepro-claude-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/imaginpro/imaginepro-claude-plugin/agents-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.00367 | $0.00367 |
| Opus 5.5 | $0.00147 | $0.00147 |
| Sonnet 5.5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
imaginepro-claude-plugin 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 1mo 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.
What it actually says
Agent Guidelines for ImaginePro Claude Plugin
Build/Lint/Test Commands
This is a documentation-only plugin with no build process. Validation commands:
- Validate plugin structure: Check
.claude-plugin/plugin.jsonfor valid JSON syntax - Verify MCP config: Ensure
.mcp.jsonreferences correct npm package version - Test links: Validate all internal documentation links work
- Preview markdown: Check agent/command files render properly
Code Style Guidelines
JSON Files
- Use 2-space indentation
- Sort object keys alphabetically where possible
- Include trailing commas for multi-line arrays/objects
- Use double quotes for strings
Markdown Files
- Use
#for main headers,##for sections,###for subsections - Use bullet points (
-) for lists, numbered lists (1.) for sequences - Use code blocks with language specifiers for examples
- Keep lines under 100 characters where possible
- Use consistent heading capitalization (Title Case)
File Naming
- Use kebab-case for file names (e.g.,
web-asset-producer.md) - Agent files: descriptive names ending with role (e.g.,
marketing-creative.md) - Command files: action-oriented names (e.g.,
imagine-pro.md)
Content Structure
- Agents: Follow Expertise → Workflow → Best Practices → Examples format
- Commands: Purpose → Usage → Examples → Tips structure
- Include specific technical specs (dimensions, formats, tools)
- Reference MCP tools by exact names from imaginepro-mcp-server
Error Handling
- Validate JSON syntax before committing changes
- Check all internal links in documentation
- Ensure examples are accurate and tested
- Follow semantic versioning for plugin updates
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.
- 1mo ago First seen · 42 lines · 367 tokens per session scan A 0bcc508ecffd
imaginepro-claude-plugin AGENTS.md is an instructions file published in the GitHub repository imaginpro/imaginepro-claude-plugin (5 stars, last pushed 1y ago), licensed MIT. It adds 367 tokens to every session, about $0.0015 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.