Borrowing it
Nothing to install: this file belongs to jeffh/claude-plugins. 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/jeffh/claude-plugins/main/CLAUDE.mdgit clone --depth 1 https://github.com/jeffh/claude-pluginsWrote 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/jeffh/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/jeffh/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/jeffh/claude-plugins/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.
<a href="https://agentmods.dev/instructions/jeffh/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/jeffh/claude-plugins/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01189 | $0.01189 |
| Opus 5.5 | $0.00476 | $0.00476 |
| Sonnet 5.5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
claude-plugins 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 1mo 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 — 134 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.
Repository Overview
This repository contains Claude Code plugins organized as a marketplace. The primary plugin is humanlayer, which provides specialized commands and agents for enhanced codebase research, planning, and implementation workflows.
Repository Structure
.claude-plugin/
marketplace.json # Plugin marketplace configuration
humanlayer/
agents/ # Specialized sub-agents for Task tool
commands/ # Slash commands for Claude Code
Plugin Architecture
Marketplace Configuration
The .claude-plugin/marketplace.json file defines available plugins:
- Name: jeffh-claude-plugins
- Primary plugin: humanlayer (commands and agents from HumanLayer, without thought syncing)
HumanLayer Plugin Components
Agents (in humanlayer/agents/)
Specialized sub-agents designed to be invoked via the Task tool. Each agent has a specific role:
- codebase-analyzer: Analyzes implementation details with file:line references. Documents HOW code works without suggesting improvements.
- codebase-locator: Finds WHERE code lives in the codebase. Returns file locations organized by purpose.
- codebase-pattern-finder: Finds similar implementations and usage examples. Shows existing patterns as reference.
- thoughts-analyzer: Deep dives on research topics within the thoughts/ directory.
- thoughts-locator: Discovers relevant documents in thoughts/ directory.
- web-search-researcher: Performs web research using WebSearch and WebFetch tools.
Key principle: All agents are documentarians, not critics. They describe what exists without suggesting improvements unless explicitly asked.
Commands (in humanlayer/commands/)
Slash commands that implement complete workflows:
- /commit: Creates git commits for session changes. Never adds Claude attribution or co-author info. Groups related changes logically.
- /create_plan: Interactive planning process that researches codebase, asks clarifying questions, and generates implementation plans in
thoughts/shared/plans/. - /implement_plan: Executes approved implementation plans phase-by-phase with automated and manual verification checkpoints.
- /validate_plan: Validates implementation against plan success criteria, running automated checks and identifying manual testing requirements.
- /describe_pr: Generates comprehensive PR descriptions using template from
thoughts/shared/pr_description.md, runs verification steps, and updates PR. - /research_codebase: Spawns parallel sub-agents to comprehensively research codebase questions and generates documentation in
thoughts/shared/research/.
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.
- 1mo ago First seen · 134 lines · 1,189 tokens per session scan A aa5c01e8c14e
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 9d ago), licensed Apache-2.0. It adds 1,189 tokens to every session, about $0.0048 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.