Borrowing it
Nothing to install: this file belongs to musharna/plantcv-mcp. 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/musharna/plantcv-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/musharna/plantcv-mcpWrote 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/musharna/plantcv-mcp/claude-md)<a href="https://agentmods.dev/instructions/musharna/plantcv-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/musharna/plantcv-mcp/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/musharna/plantcv-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/musharna/plantcv-mcp/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.00745 | $0.00745 |
| Opus 5 | $0.00373 | $0.00373 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
plantcv-mcp 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 2d 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.
This is a copy
100% identical to plant-genomics-mcp CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The bar for code in this repo
Most code here is machine-written. It is held to a HIGHER bar than hand-written code, not a lower one. This file is the contract; CI and the pre-commit hooks are its enforcement. Read it before writing anything.
1. Before code: outcome and constraints, in writing
State, in the PR description or the issue, before the first line of code:
- Outcome: the observable behaviour that will exist when this is done.
- Acceptance check: the command whose exit status decides done. If no such command exists yet, writing it is the first task.
- Constraints: what must not change (public API, file formats, data on disk, runtime budget), and what is out of scope.
Ambiguity is a stop sign. Ask; do not pick the most likely reading.
2. A test is worth only what it can fail on
Every test ships with three controls:
- Seen to fail: run it against the broken state and confirm it fails FOR THE STATED REASON. A security test that asserts "some exception was raised" passes on vulnerable code too.
- Positive control: a negative assertion (error raised, input rejected) lives in the same test as the assertion that the legitimate path succeeds.
- Real execution at every system boundary: code that talks to a registry, a CLI, the network or another process's file layout gets at least one check that drives the real thing, not only a fixture.
A fixture encodes your belief; it cannot fail on that belief. A wall-clock
budget cannot tell a slow host from a broken test. A surviving mutant
(nightly-guardrails.yml) is the coverage report.
3. House rules (enforced; see .pre-commit-config.yaml)
Each rule is an incident, not a preference:
x.replace(a, b)with the result discarded is a silent no-op.pytest.raises(Exception)cannot tell a wrapped error from a leaked one.except ParseErrorwith defusedxml imported lets the attack path escape.# nosecnames the test id AND a traced reason.- No nested lazy quantifiers; no
nohup ... &; notext-transform: uppercaseover unit strings; no absolute developer-machine paths.
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.
- 2d ago First seen · 66 lines · 745 tokens per session scan A c230ea667c5f
plantcv-mcp CLAUDE.md is an instructions file published in the GitHub repository musharna/plantcv-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 745 tokens to every session, about $0.0037 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plant-genomics-mcp CLAUDE.md, differing in 0 lines, and is treated as a copy.
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.
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.
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).