Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/jbzoo/csv-blueprint/claude-mdgit clone --depth 1 https://github.com/JBZoo/CSV-BlueprintWrote 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/jbzoo/csv-blueprint/claude-md)<a href="https://agentmods.dev/instructions/jbzoo/csv-blueprint/claude-md"><img src="https://agentmods.dev/badge/instructions/jbzoo/csv-blueprint/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.01293 | $0.01293 |
| Opus 5 | $0.00647 | $0.00647 |
| Sonnet 5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
CSV-Blueprint 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 5d 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 — 175 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
CSV Blueprint is a CLI tool for validating CSV files based on customizable YAML schemas. It provides over 330+ validation rules that can be applied to individual cells or entire columns, with support for parallel processing and multiple output formats.
Core Architecture
The project follows a modular architecture with clear separation of concerns:
- CLI Layer:
src/Commands/- Command classes for different operations (ValidateCsv, CreateSchema, etc.) - Schema Engine:
src/Schema.php- Core schema definition and parsing - Validation Rules:
src/Rules/- Two types of validation rules:Cell/- Individual cell validation rules (~90 rules)Aggregate/- Column-wide aggregate validation rules (~44 rules)
- CSV Processing:
src/Csv/- CSV file handling and column management - Workers:
src/Workers/- Parallel processing implementation - Validators:
src/Validators/- Validation orchestration and error reporting
Key Components
- Schema Definition: YAML-based schemas define validation rules for CSV columns
- Rule System: Extensible rule system with AbstractRule base class
- Error Reporting: Multiple output formats (table, text, GitHub Actions, etc.)
- Parallel Processing: Multi-threaded validation for large files
- CLI Interface: Built with Symfony Console components
Team Collaboration & Use Cases
Contract-Based Workflow
CSV Blueprint schemas serve as a data contract between teams (similar to Swagger/OpenAPI for APIs). Recommended approach: maintain schemas and fixtures in a dedicated repository shared between Data Engineers and Backend Engineers.
Recommended schema repository structure:
schemas/
├── exports/ # Schemas for outgoing data
│ └── *.yml
└── imports/ # Schemas for incoming data
└── *.yml
fixtures/
└── *.csv # Sample files for testing
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.
- 5d ago First seen · 175 lines · 1,293 tokens per session scan A 96e9f84685f5
CSV-Blueprint CLAUDE.md is an instructions file published in the GitHub repository JBZoo/CSV-Blueprint (57 stars, last pushed 1mo ago), licensed MIT. It adds 1,293 tokens to every session, about $0.0065 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
sq AGENTS.md
Instructions for neilotoole/sq, covering agents.md, about sq, key documents, common commands and conventions.
comma copilot-instructions.md
Copilot instructions for comma-csv/comma, covering copilot instructions for comma, build, test, and lint commands, install dependencies for the base gemfile, install all appraisal gemfiles used by ci and build the gem.
sq CLAUDE.md
Instructions for neilotoole/sq: Claude Code entry point for this repo. Shared rules live in AGENTS.md.
dbcrust CLAUDE.md
Instructions for clement-tourriere/dbcrust, covering claude.md, build commands, python bindings, gui (tauri) and module map.
dbcrust AGENTS.md
Instructions for clement-tourriere/dbcrust, covering agents.md - development guide for dbcrust, build/lint/test commands, core build commands, install bun-managed gui dependencies and build the project (development).
qsv CLAUDE.md
Claude Code instructions for dathere/qsv, covering claude.md, general rules, documentation, tools & commands and workflow requirements.