Borrowing it
Nothing to install: this file belongs to kleer001/nuke-mcp. 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/kleer001/nuke-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/kleer001/nuke-mcpWrote 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/kleer001/nuke-mcp/claude-md)<a href="https://agentmods.dev/instructions/kleer001/nuke-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kleer001/nuke-mcp/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.00574 | $0.00574 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
nuke-mcp 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NukeMCP — AI Behavior Rules
You are connected to a live Nuke compositing session via MCP. Follow these rules.
Architecture
Three-layer system:
- Nuke Addon — socket server running inside Nuke (port 54321)
- MCP Server (
src/nukemcp/) — FastMCP bridge, exposes tools via stdio - AI Client — you, reading this file
Destructive Actions
Never perform destructive actions without explicit user confirmation:
delete_node— always call first withconfirm=Falseto show what would be deleted, then confirm with the user before calling withconfirm=Trueexecute_python— always show the code to the user first, then confirm before calling withconfirm=Trueload_script— always warn that the current script will be replaced, then confirm
The pattern:
- Call the tool with
confirm=False(returns a description of what would happen) - Show the description to the user
- Ask for confirmation
- Only if confirmed, call again with
confirm=True
Before Making Changes
- Call
get_script_infoto understand the current state - Call
get_node_infoon relevant nodes before modifying them - Never assume what nodes exist — always check first
- Read error messages carefully; they tell you what went wrong
Node Naming
Use descriptive, lowercase names with underscores:
fg_keynotKeyer1bg_gradenotGrade3hero_mergenotMerge1plate_readnotRead1
Node Organization
- Keep the graph flowing top-to-bottom
- Source nodes (Read) at the top, output nodes (Write) at the bottom
- Use
auto_layoutafter creating multi-node setups - Position related nodes near each other
Colorspace
- Respect the project's working colorspace — check with
get_script_info - Never change colorspace settings without asking
- When creating Read nodes, mention the expected colorspace if relevant
Memory
- On session start, read
nuke://memory/facilityandnuke://memory/correctionsresources for context - After any correction by the compositor, call
log_correctionto persist it for future sessions - Periodically call
update_project_memoryto keep the project snapshot current - If facility conventions exist, follow them (colorspace, naming, preferred tools)
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.
- 8d ago First seen · 66 lines · 574 tokens per session scan A 4549e3e44560
nuke-mcp CLAUDE.md is an instructions file published in the GitHub repository kleer001/nuke-mcp (9 stars, last pushed 5mo ago), licensed MIT. It adds 574 tokens to every session, about $0.0029 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
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).
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.
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.