Borrowing it
Nothing to install: this file belongs to ryansmith4/sheriff-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/ryansmith4/sheriff-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ryansmith4/sheriff-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/ryansmith4/sheriff-mcp/claude-md)<a href="https://agentmods.dev/instructions/ryansmith4/sheriff-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ryansmith4/sheriff-mcp/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.1 | $0.02186 | $0.02186 |
| Opus 5 | $0.01093 | $0.01093 |
| Sonnet 5 | $0.00437 | $0.00437 |
| Haiku 4.5 | $0.00219 | $0.00219 |
Grade A, and why
sheriff-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 7d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sheriff-MCP Development Guide
Project Overview
Sheriff-MCP is a Java MCP server for parsing and querying SARIF static analysis reports. It's designed as an AI agent work queue manager for efficiently fixing static analysis issues.
Current Version: Run ./gradlew currentVersion
Versioning
Sheriff-MCP follows Semantic Versioning 2.0.0 via the axion-release-plugin:
- MAJOR version (X.0.0): Incompatible API changes, breaking changes to MCP tool interface
- MINOR version (0.X.0): New functionality in a backwards-compatible manner
- PATCH version (0.0.X): Backwards-compatible bug fixes
Version Source
Version is derived from git tags — there is no version in any file. The plugin reads the nearest v* tag and computes:
- On a tagged commit (release):
1.0.0 - After a tagged commit (development):
1.0.1-SNAPSHOT
This version is used by all build tools: Gradle, JReleaser, Jib, MCP Registry, and Java runtime (via generated version.properties).
Release Process
./gradlew release # Patch release (1.0.0 → 1.0.1)
./gradlew release -Prelease.increment=minor # Minor release (1.0.0 → 1.1.0)
./gradlew release -Prelease.increment=major # Major release (1.0.0 → 2.0.0)
./gradlew release -Prelease.forceVersion=2.0.0 # Explicit version
./gradlew release -Prelease.prerelease=beta # Pre-release (1.0.0-beta1)
./gradlew release -Prelease.prerelease=rc # Release candidate (1.0.0-rc1)
The release task creates a git tag (e.g., v1.0.0) and pushes it. No version-bump commits are created.
The tag push triggers the CI/CD pipeline (release.yml):
releasejob: Builds, runs JReleaser (GitHub Release + Sigstore signing) — runs for all tagsdockerjob: Builds and pushes multi-arch Docker image toghcr.io/ryansmith4/sheriff-mcpvia Jib — final releases onlymcp-registryjob: Publishes to the MCP Registry viamcp-publisher— final releases onlydocsworkflow: Deploys documentation to GitHub Pages
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.
- 7d ago First seen · 179 lines · 2,186 tokens per session scan A 1f316fb1a4a7
sheriff-mcp CLAUDE.md is an instructions file published in the GitHub repository ryansmith4/sheriff-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,186 tokens to every session, about $0.0109 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
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
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.
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.
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).