Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/instructions/fortiumpartners/ensemble/claude-md)<a href="https://agentmods.dev/instructions/fortiumpartners/ensemble/claude-md"><img src="https://agentmods.dev/badge/instructions/fortiumpartners/ensemble/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.03301 | $0.03301 |
| Opus 5 | $0.01650 | $0.01650 |
| Sonnet 5 | $0.00660 | $0.00660 |
| Haiku 4.5 | $0.00330 | $0.00330 |
Grade A, and why
ensemble 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 6d 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Plugins - Claude Code Configuration
Modular plugin ecosystem for Claude Code (v5.1.0) | 23 packages | 28 agents | 4-tier architecture
Quick Reference
Slash Commands
All ensemble commands use the /ensemble: namespace:
/ensemble:fold-prompt # Optimize Claude environment
/ensemble:create-prd # Create Product Requirements Document
/ensemble:create-trd # Create Technical Requirements Document
/ensemble:create-trd-foreman # Create Foreman-native structured Technical Requirements Document
/ensemble:implement-trd # Implement TRD with git-town workflow
/ensemble:fix-issue # Lightweight bug fix workflow (analysis → PR)
/ensemble:release # Orchestrate release workflow
/ensemble:playwright-test # Run E2E tests with Playwright
/ensemble:sessionlog # Save structured session transcript
/ensemble:manager-dashboard # Generate productivity metrics
/ensemble:sprint-status # Current sprint status report
Essential Commands
npm test # Run all tests
npm run validate # Validate marketplace + plugins
npm run generate # Regenerate markdown from YAML
npm run generate:opencode # Generate OpenCode-compatible artifacts from Ensemble plugins
npm run test:coverage # Coverage reports
Key Paths
- Plugins:
packages/*/(24 packages) - Agents:
packages/*/agents/*.yaml(28 agents) - Commands:
packages/*/commands/ - Skills:
packages/*/skills/ - Schemas:
schemas/{plugin,marketplace}-schema.json - OpenCode Output:
dist/opencode/(generated artifacts for OpenCode runtime)
OpenCode Support
Ensemble plugins can be translated for use with the OpenCode runtime via npm run generate:opencode.
This generates OpenCode-compatible skills, commands, and config in dist/opencode/. Supports
--dry-run, --verbose, --validate, and --force flags. See packages/opencode/ for the
translation layer implementation.
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.
- 6d ago First seen · 413 lines · 3,301 tokens per session scan A da2eee31e9ac
ensemble CLAUDE.md is an instructions file published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 3,301 tokens to every session, about $0.0165 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
claude-prompts-mcp CLAUDE.md
Claude Code instructions for minipuft/claude-prompts-mcp, covering claude prompts mcp -- operator handbook, core principles, node.js support boundaries, validation gates (one contract, impact-aware subsets) and fleet standards upstream (minipuft/repository-standards).
claude-prompts-mcp AGENTS.md
AGENTS.md instructions for minipuft/claude-prompts-mcp, covering agent rules · claude prompts mcp, canonical ownership and loading, core principles, node.js support boundaries and validation gates (one contract, impact-aware subsets).
agent-11 CLAUDE.md
Claude Code instructions for TheWayWithin/agent-11, covering agent-11 framework repository, quick reference, how to work with me, my brain works differently (adhd) and what i need from instructions.
Silex AGENTS.md
AGENTS.md instructions for silexlabs/Silex, covering agents.md, tech stack, run it locally, building the desktop app and when writing code for silex (editing source).
voltagent CLAUDE.md
Instructions for VoltAgent/voltagent, a project described as: AI Agent Engineering Platform built on an Open Source TypeScript AI Agent Framework.
js-bson CLAUDE.md
Claude Code instructions for mongodb/js-bson, a project described as: BSON Parser for node and browser.