Borrowing it
Nothing to install: this file belongs to mishoko/solidity-auditor-pulse. 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/mishoko/solidity-auditor-pulse/main/CLAUDE.mdgit clone --depth 1 https://github.com/mishoko/solidity-auditor-pulseWrote 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/mishoko/solidity-auditor-pulse/claude-md)<a href="https://agentmods.dev/instructions/mishoko/solidity-auditor-pulse/claude-md"><img src="https://agentmods.dev/badge/instructions/mishoko/solidity-auditor-pulse/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.03752 | $0.03752 |
| Opus 5 | $0.01876 | $0.01876 |
| Sonnet 5 | $0.00750 | $0.00750 |
| Haiku 4.5 | $0.00375 | $0.00375 |
Grade A, and why
solidity-auditor-pulse CLAUDE.md scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `claude` CLI installed (all LLM calls use the CLI binary via `child_process.spawn` — no Anthropic SDK) How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Benchmark Runner
What This Is
CLI tool that benchmarks Claude Code audit skills against each other amd/or a bare Claude Code baseline/bare. Runs multiple iterations of each condition against real Solidity codebases, captures raw output, verifies execution integrity, and generates comparison reports with recall/FP scoring against ground truth.
Setup Requirements
- Node 20+
claudeCLI installed (all LLM calls use the CLI binary viachild_process.spawn— no Anthropic SDK)- Exclude
results/andworkspaces/from cloud sync (Dropbox, iCloud, OneDrive). File sync during benchmark writes causes data corruption — see Platform Limitations. Runnpm run setupto create.nosyncmarkers.
Quickstart
# 0. First-time setup (creates .nosync markers for sync protection)
npm run setup
# 1. Run benchmark
npm run bench -- --codebases merkl-stripped --runs 3 --parallel
# 2. Analyze results (classify → cluster → validate → report)
npm run analyze
# 3. Read the results
cat summary.md
# 4. Management dashboard (optional, no LLM calls)
npm run dashboard
open dashboard.html
Project Structure
src/
shared/ Types, parser, utilities — shared across all modules
types.ts Central type definitions
report-data.ts Shared data feed (ReportData) — single source of truth for all renderers
parser.ts Finding extraction from raw audit output
util/ Logger, shell helpers, hash utility
runner/ Benchmark execution — spawns claude, captures output
cli.ts CLI entrypoint (npm run bench)
config.ts Config loader (bench.json)
runner.ts Main benchmark loop
workspace.ts Workspace creation (real copies per condition)
skill.ts Skill version management
verify.ts Post-run verification (12 checks)
classifier/ Analysis pipeline — independent from runner
llm.ts LLM call utility with injectable LLMProvider (CLI default, fake for tests)
classify.ts GT classification with configurable Nx majority vote
cluster.ts Novel finding clustering (incremental + chunked full)
validate.ts Novel validation against scoped source code
pipeline.ts Orchestrator: classify → cluster → validate
pipeline-cli.ts CLI entrypoint (npm run analyze)
reports/ Report generation — consumes shared data feed
report.ts Markdown renderer (deterministic tables + LLM narrative)
report-cli.ts CLI entrypoint (npm run report)
dashboard/ Management HTML dashboard — consumes same shared data feed
render.ts HTML renderer (npm run dashboard)
archive/ Result archival with provenance manifest
archive.ts Core archive logic (npm run archive)
config/ JSON benchmark configs (bench.json)
datasets/ Solidity codebases to audit (submodules + canary inline)
skills_versions/ Pinned skill snapshots (pashov/, darknavy/, each with source.json provenance)
workspaces/ Ephemeral real-copy workspaces (gitignored, auto-cleaned)
results/ Run outputs + report-data.json shared feed (gitignored)
ground_truth/ Known-bug answer keys per codebase (JSON, enables Recall/FP scoring)
ground_truth/reports/ Official C4 audit reports (markdown)
docs/ Isolation strategy, benchmark prompt template, rewrite plan, testing strategy
archive-results/ Archived result snapshots with MANIFEST.json (gitignored)
tests/ Vitest test suite (275 tests, 17 files)
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.
- 8d ago First seen · 303 lines · 3,752 tokens per session scan A 5f9795d93303
solidity-auditor-pulse CLAUDE.md is an instructions file published in the GitHub repository mishoko/solidity-auditor-pulse (3 stars, last pushed 5mo ago), licensed MIT. It adds 3,752 tokens to every session, about $0.0188 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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).
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).
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.
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.