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/laurigates/claude-plugins/claude-mdgit clone --depth 1 https://github.com/laurigates/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/laurigates/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/laurigates/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/laurigates/claude-plugins/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 | $0.03676 | $0.03676 |
| Opus 5 | $0.01838 | $0.01838 |
| Sonnet 5 | $0.00735 | $0.00735 |
| Haiku 4.5 | $0.00368 | $0.00368 |
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 today.
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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-plugins
Claude Code plugin collection providing skills and agents for development workflows.
Project Structure
<plugin-name>/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest (see .claude/rules/plugin-structure.md)
├── README.md # Plugin documentation
├── CHANGELOG.md # Auto-generated by release-please
├── skills/
│ └── <skill-name>/
│ ├── SKILL.md # Skill definition (user-invocable and auto-discovered)
│ └── workflows/ # Bundled *.workflow.js templates (optional)
└── agents/ # Agent definitions (optional)
Rules
| Rule | Purpose |
|---|---|
.claude/rules/conventional-commits.md |
Commit and PR title format standards - drives release-please automation |
.claude/rules/plugin-structure.md |
plugin.json schema and directory layout |
.claude/rules/release-please.md |
Version management and changelog automation |
.claude/rules/skill-development.md |
Skill creation patterns |
.claude/rules/skill-consolidation.md |
Merging/deleting skills: verify the premise first, cross-plugin = name-reference (not shared REFERENCE.md), and the merge/delete checklist |
.claude/rules/agentic-optimization.md |
CLI output optimization for AI |
.claude/rules/skill-naming.md |
Skill namespace conventions |
.claude/rules/shell-scripting.md |
Safe shell patterns and frontmatter extraction |
.claude/rules/agentic-permissions.md |
Granular tool permissions for skills |
.claude/rules/auto-mode.md |
Auto mode availability, classifier rules, allow-rule fate, and authoring guidance |
.claude/rules/skill-quality.md |
Skill size limits, required sections, and quality checklist |
.claude/rules/skill-argument-handling.md |
9-axis rubric for args/argument-hint/parsing-vs-intent fit; the haiku+opus cold-read sweep that finds mismatches and the model delta that calibrates it |
.claude/rules/skill-execution-structure.md |
Imperative execution patterns for user-invocable skills |
.claude/rules/handling-blocked-hooks.md |
How to respond when hooks block commands |
.claude/rules/hook-block-vs-nudge.md |
Block (exit 2) only for safety; nudge for style — why a hard block on a tool-substitution dead-ends subagents lacking the tool, and the "what does it exempt?" litigation test |
.claude/rules/hooks-reference.md |
Complete hook event reference (2.1.50+): all events, schemas, timeouts, PermissionRequest |
.claude/rules/prompt-agent-hooks.md |
When to use prompt/agent hooks — decision tree, config schema, prompts guide |
.claude/rules/agent-development.md |
Agent configuration, isolation, background execution, memory, and teams |
.claude/rules/skill-fork-context.md |
When to set context: fork and agent: on skills |
.claude/rules/workflow-vs-skill.md |
When a bundled workflow .js earns its agents — enumerable N, real barrier, script-decidable bound; the workflows/ layout |
.claude/rules/regression-testing.md |
Required: add a script check for every skill bug fixed |
.claude/rules/skill-evaluation.md |
How we measure skill effectiveness: tiered cost, deterministic-vs-judge grading, cross-model delta signal |
.claude/rules/context-engineering.md |
Claude 5 context-engineering position — rank cuts by always-loaded cost, scope new rules with paths:, split large skills across many files; demotes three skill-quality.md mandates |
.claude/rules/sandbox-guidance.md |
Sandbox constraints, CLAUDE_CODE_REMOTE detection, and remote/local skill patterns |
.claude/rules/plugin-flow-diagrams.md |
When and how to add Mermaid flow diagrams |
.claude/rules/agent-coworker-detection.md |
Detect other agents working in the same repo clone before destructive git ops |
.claude/rules/pr-branch-sync.md |
Before building further on a PR branch, confirm it's live and in sync (remote sibling of coworker-detection) — the /git:pr-sync-check skill + check-branch-sync-on-push.sh hook + git-drift-probe.sh trio |
.claude/rules/workflow-naming.md |
<Domain>: <Action> naming for .github/workflows/*.yml and skill-generated workflow examples |
.claude/rules/github-actions-security.md |
GitHub Actions secure-use baseline — least-privilege GITHUB_TOKEN, script-injection env-var indirection, pull_request_target hazards, CODEOWNERS on workflows; the checklist every workflow-scaffolding skill follows |
.claude/rules/workflow-model-effort.md |
Workflow Claude model/effort standard — every .github/workflows invocation pins --model opus + explicit --effort (cost-economics, not the subagent-contamination argument); enforced by check-workflow-model.sh |
.claude/rules/bash-tool-replacements.md |
find/grep/rg/cat/head/tail → dedicated tools; when the Bash form is genuinely fine |
.claude/rules/gh-json-fields.md |
Correct gh --json field names (PR state/mergedAt, not merged); --limit and head: truncation traps |
.claude/rules/structured-script-output.md |
=== HEADER === / KEY=VALUE / STATUS= convention for diagnostic shell scripts |
.claude/rules/terminology.md |
Glossary of development terms with strong intent (scoping, review, parallelism, work state, code ops, requirements) — positive definitions with Use when disambiguation |
.claude/rules/parallel-safe-queries.md |
Query commands that exit non-zero on empty results silently cancel sibling parallel tool calls — use the machine-readable variant (--json/export + jq) |
.claude/rules/docs-currency.md |
Code and the docs describing it land in the same commit (stub → blueprint:blueprint-docs-currency) |
.claude/rules/version-pinning.md |
Version pins in skill examples (uses:/FROM/image:/rev:) are a Renovate-managed surface — SHA+comment convention, the coverage guard, and what's illustrative vs. managed |
.claude/rules/loop-integrity.md |
Long-running/self-continuing loops need an independent stop condition (a fresh verifier judges "done", not the worker) and a compact state packet each iteration (objective/ref/files/verifier-result/changed-since/exit-condition) — else they optimize for completion over correctness or automate context drift |
.claude/rules/gitattributes.md |
.gitattributes conventions — merge=union only for one-line-per-entry append-only files, linguist-generated for build output (always safe), LF normalization; the configure-gitattributes skill + resolve-additive-conflicts.py pre-pass |
.claude/rules/task-id-stability.md |
Taskwarrior numeric IDs renumber after every close — resolve the immutable UUID once and mutate by UUID, including within a single skill's own multi-step lifecycle, not just across bulk loops |
.claude/rules/generated-fleet-drift.md |
Auditing a generated fleet — divergence is not automatically drift: it is bidirectional (never auto-apply template → instance), an identically-diverging cohort signals intent, and undeclared intent is unauditable |
.claude/rules/plugin-usage-telemetry.md |
~/.claude.json's pluginUsage.usageCount counts hook fires, so it ranks trigger cadence rather than plugin value — nothing in this repo reads it (incl. health-check --scope=usage, which mines transcripts); the delivery signal is the lowercase-first attributionPlugin/attributionSkill/attributionAgent |
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.
- today Changed · -2 lines · -95 tokens per session 3135f939d312
- 4d ago First seen · 182 lines · 3,771 tokens per session scan A 2d0725871404
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed today), licensed MIT. It adds 3,676 tokens to every session, about $0.0184 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
code-virtuoso CLAUDE.md
Claude Code instructions for krzysztofsurdy/code-virtuoso, covering code virtuoso - claude code instructions, claude code tool mapping, skill research process, marketplace configuration and commit conventions.
agentenv Development Guide
Development areas and conventions across the Rust CLI, core library, and VS Code extension.
awesome-ai-coe AGENTS.md
AGENTS.md instructions for frankxai/awesome-ai-coe, covering repository instructions, classification, agent rules, class-specific guidance and handoff.
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).
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.
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.