Use them when browsing files, selecting code, asking RepoPrompt for a review, reading its responses, or applying its suggested edits.

They prevent developers from using the unavailable command-line tool and explain the required workflow for building review context.

How Ranudar/devcontainer-for-claude-yolo-and-flow-next configures Clau

Q: What is devcontainer-for-claude-yolo-and-flow-next CLAUDE.md?

Project instructions for using RepoPrompt, a tool that selects repository files and sends their contents to an AI for tasks such as code review.

Reuse

Borrowing it

Nothing to install: this file belongs to Ranudar/devcontainer-for-claude-yolo-and-flow-next. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Ranudar/devcontainer-for-claude-yolo-and-flow-next/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Ranudar/devcontainer-for-claude-yolo-and-flow-next

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ranudar/devcontainer-for-claude-yolo-and-flow-next/claude-md/github.svg)](https://agentmods.dev/instructions/ranudar/devcontainer-for-claude-yolo-and-flow-next/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/ranudar/devcontainer-for-claude-yolo-and-flow-next/claude-md"><img src="https://agentmods.dev/badge/instructions/ranudar/devcontainer-for-claude-yolo-and-flow-next/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ranudar/devcontainer-for-claude-yolo-and-flow-next/claude-md"><img src="https://agentmods.dev/badge/instructions/ranudar/devcontainer-for-claude-yolo-and-flow-next/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 856 This file is loaded in full into every session.

When invoked 856 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00856	$0.00856
Opus 5	$0.00428	$0.00428
Sonnet 5	$0.00171	$0.00171
Haiku 4.5	$0.00086	$0.00086

Measured 10d ago against content hash 7644df970663, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

devcontainer-for-claude-yolo-and-flow-next 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.

CLAUDE.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Notes

CRITICAL: RepoPrompt MCP (NOT rp-cli)

In this devcontainer, rp-cli is NOT available. RepoPrompt is accessed via MCP server through mcp-proxy on the Mac host.

How to Use RepoPrompt

Use the MCP tools directly (these are available in Claude Code):

mcp__RepoPrompt__manage_selection    # Select files for context
mcp__RepoPrompt__workspace_context   # Get current context snapshot
mcp__RepoPrompt__chat_send           # Send to RepoPrompt chat (GPT-5.2, etc.)
mcp__RepoPrompt__get_file_tree       # Browse file tree
mcp__RepoPrompt__file_search         # Search files
mcp__RepoPrompt__read_file           # Read file contents
mcp__RepoPrompt__apply_edits         # Apply code edits
mcp__RepoPrompt__prompt              # Get/set the prompt
mcp__RepoPrompt__chats               # List/view chat history
mcp__RepoPrompt__list_models         # List available models
mcp__RepoPrompt__get_code_structure  # Get codemaps
mcp__RepoPrompt__context_builder     # AI-assisted context building

For Code Reviews via RepoPrompt

# 1. Select the files to review
mcp__RepoPrompt__manage_selection(op="set", paths=["file1.py", "file2.py"])

# 2. Set the review prompt
mcp__RepoPrompt__prompt(op="set", text="Review this code for security issues...")

# 3. Send to chat with review mode
mcp__RepoPrompt__chat_send(new_chat=True, mode="review", message="Review the selected files")

# 4. Get the response
mcp__RepoPrompt__chats(action="log", chat_id="...")

What Does NOT Work

rp-cli - NOT installed in container
flowctl rp commands - these shell out to rp-cli which doesn't exist
Any direct CLI access to RepoPrompt

flow-next Review Backend

When flow-next asks for a review backend:

Use RepoPrompt MCP tools directly (preferred) - as shown above
Use "codex" only if RepoPrompt MCP is unavailable
Do NOT choose "rp" (RepoPrompt CLI) - it doesn't exist in this container

Priority: RepoPrompt MCP > Codex CLI > none

Read the full file on GitHub · 92 lines

Changes

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 · 92 lines · 856 tokens per session scan A 7644df970663

Subscribe to this mod's changes

devcontainer-for-claude-yolo-and-flow-next CLAUDE.md is an instructions file published in the GitHub repository Ranudar/devcontainer-for-claude-yolo-and-flow-next (4 stars, last pushed 7mo ago), licensed MIT. It adds 856 tokens to every session, about $0.0043 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.

Code review claude code dangerously-skip-permissions docker firewall flow-next

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

devcontainer-for-claude-yolo-and-flow-next: Instructions file for Claude Code