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/stilero/claude-plugins/claude-mdgit clone --depth 1 https://github.com/stilero/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/stilero/claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/stilero/claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/stilero/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.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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 3d 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 — 53 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.
What This Is
A Claude Code plugin marketplace repository (stilero/claude-plugins). Contains multiple independent plugins distributed via /plugin marketplace add stilero/claude-plugins. There is no build system, package manager, or test suite — plugins are pure markdown/JSON.
Repository Structure
plugins/
<plugin-name>/
.claude-plugin/
plugin.json # Required manifest (name, description, version, author)
commands/ # Slash commands (markdown files)
agents/ # Subagent definitions (markdown files)
skills/ # Skill definitions (SKILL.md with YAML frontmatter)
<skill-name>/
SKILL.md
references/ # Optional supporting docs
.mcp.json # Optional MCP server config
README.md
Current Plugins
- pr-comment-fixer — Fetches and fixes unresolved GitHub PR review comments. Has a skill and a slash command.
- hardcore-code-reviewer — Strict code reviewer that spawns 12 parallel subagents (bug-hunter, security-reviewer, architecture-reviewer, test-reviewer, silent-failure-hunter, performance-reviewer, complexity-reviewer, observability-reviewer, api-contract-reviewer, data-migration-reviewer, accessibility-reviewer, type-safety-reviewer). Has a skill, a command, and 12 agent definitions.
- shopify-apps — Guidance for Shopify app development. Has a skill with reference docs.
- github-issue-generator — Evaluates conversation findings and creates/updates GitHub issues with duplicate checking.
- obsidian-knowledge-bank — Persistent indexed knowledge bank for learnings, ADRs, technical context, and session notes.
- tech-debt-audit — Spawns 11 parallel agents to audit a codebase for technical debt, groups findings into actionable issues, and offers GitHub issue creation.
Plugin Conventions
plugin.jsonis the only required file — it lives in.claude-plugin/.- Skills use YAML frontmatter (
name,description) inSKILL.md. Thedescriptionfield is critical for triggering — it must clearly describe when the skill should activate. - Agent markdown files define subagent behavior with YAML frontmatter specifying tools, model, and description.
- Commands are markdown files with YAML frontmatter (
description, optionalallowed-tools). - No code compilation or dependencies. All plugin logic is expressed as markdown prompts.
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.
- 3d ago First seen · 53 lines · 689 tokens per session scan A 5398225f9232
claude-plugins CLAUDE.md is an instructions file published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 689 tokens to every session, about $0.0034 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-31.
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).
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.