Borrowing it
Nothing to install: this file belongs to itsdevcoffee/plum. 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/itsdevcoffee/plum/main/CLAUDE.mdgit clone --depth 1 https://github.com/itsdevcoffee/plumWrote 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/itsdevcoffee/plum/claude-md)<a href="https://agentmods.dev/instructions/itsdevcoffee/plum/claude-md"><img src="https://agentmods.dev/badge/instructions/itsdevcoffee/plum/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/itsdevcoffee/plum/claude-md"><img src="https://agentmods.dev/badge/instructions/itsdevcoffee/plum/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.00506 | $0.00506 |
| Opus 5.5 | $0.00202 | $0.00202 |
| Sonnet 5.5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
plum 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 2mo 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.
What it actually says
Plum Project Guide
Pre-Push Checklist
ALWAYS run before pushing to main:
# 1. Run linter (must pass)
golangci-lint run --timeout=5m
# 2. Run tests (must pass)
go test ./...
# 3. Verify build succeeds
go build -o ./plum ./cmd/plum
# 4. Run integration tests (optional but recommended for settings changes)
go test -tags=integration ./internal/integration/... -v
If linter is not installed:
go install github.com/golangci/golangci-lint/v2/cmd/[email protected]
Routine Maintenance
At the start of each session, check marketplace data freshness:
# 1. Update GitHub stats (stars, forks, last updated)
bash scripts/update-marketplace-stats.sh
# 2. Check plugin counts from live manifests
go run scripts/check-plugin-counts.go
If changes detected:
- Update
internal/marketplace/discovery.gowith new stats and plugin counts - Update
README.mdmarketplace table with accurate counts - Update total plugin count in README intro and features section
- Run pre-push checklist above
Why This Matters
- Linting - CI will fail if linting doesn't pass locally. Always lint before pushing.
- Accurate Data - The README is users' first impression. Accurate plugin counts and GitHub stats help them make informed decisions about installation.
Documentation
Files go in docs/ except for obvious exceptions: README.md, CLAUDE.md, LICENSE.md, CONTRIBUTING.md, AGENT.md, ... (root only).
Subdirectories:
context/- Architecture, domain knowledge, static referencedecisions/- Architecture Decision Records (ADRs)handoff/- Session state for development continuityproject/- Planning: todos, features, roadmapresearch/- Explorations, comparisons, technical analysistmp/- Scratch files (safe to delete)
Naming: YYYY-MM-DD-descriptive-name.md (lowercase, hyphens)
Rules:
- Update existing docs before creating new ones
- Use
tmp/when uncertain, flag for review
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.
- 2mo ago First seen · 70 lines · 506 tokens per session scan A afb1157df8ec
plum CLAUDE.md is an instructions file published in the GitHub repository itsdevcoffee/plum (11 stars, last pushed 8mo ago), licensed MIT. It adds 506 tokens to every session, about $0.0020 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.