Borrowing it
Nothing to install: this file belongs to jasonjgardner/blockbench-mcp-project. 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/jasonjgardner/blockbench-mcp-project/main/CLAUDE.mdgit clone --depth 1 https://github.com/jasonjgardner/blockbench-mcp-projectWrote 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/jasonjgardner/blockbench-mcp-project/claude-md)<a href="https://agentmods.dev/instructions/jasonjgardner/blockbench-mcp-project/claude-md"><img src="https://agentmods.dev/badge/instructions/jasonjgardner/blockbench-mcp-project/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.00546 | $0.00546 |
| Opus 5 | $0.00273 | $0.00273 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
blockbench-mcp-project 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 — 62 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 a Blockbench MCP (Model Context Protocol) sample project that serves as a template for creating workspaces compatible with the Blockbench MCP server. The repository contains Minecraft resource pack assets designed for use with Blockbench modeling software.
Project Structure
resource_pack/
├── models/
│ ├── blocks/ # Block geometry definitions
│ │ └── basic_block.geo.json
│ └── entity/ # Entity geometry definitions
│ └── llama.geo.json
└── textures/
├── blocks/ # Block textures and materials
│ ├── block.texture_set.json
│ ├── block_mer.png
│ ├── block_normal.png
│ └── block_texture.png
└── entity/ # Entity textures
└── llama.png
File Formats and Architecture
Geometry Files (.geo.json)
- Follow Minecraft Bedrock Edition geometry format (version 1.12.0)
- Contain bone hierarchies, pivot points, and UV mappings
- Located in
resource_pack/models/with subdirectories forblocks/andentity/
Texture Set Files (.texture_set.json)
- Define PBR material properties using format version 1.21.30
- Map color, metalness/emissive/roughness (MER), and normal textures
- Located in
resource_pack/textures/blocks/
Texture Assets
- PNG format for color, normal, and MER maps
- Standard 16x16 resolution for blocks, variable for entities
- Organized by asset type (blocks vs entities)
Development Workflow
This project contains static asset files with no build process, testing framework, or compilation steps. Changes involve:
- Geometry Editing: Modify
.geo.jsonfiles for 3D model structure - Texture Updates: Replace PNG files or update texture set configurations
- Asset Organization: Maintain the directory structure for proper resource pack function
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 · 62 lines · 546 tokens per session scan A e47b3dee5f27
blockbench-mcp-project CLAUDE.md is an instructions file published in the GitHub repository jasonjgardner/blockbench-mcp-project (15 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 546 tokens to every session, about $0.0027 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-30.
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.