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 skills/marchev/claudit/soloditnpx skills add marchev/claudit --skill soloditgit clone --depth 1 https://github.com/marchev/clauditWhat 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.00033 | $0.00807 |
| Opus 5 | $0.00016 | $0.00404 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
solodit 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solodit — Smart Contract Security Findings Search
You have access to Solodit's database of 20k+ smart contract security findings via MCP tools. Use them to find prior art, research vulnerability patterns, and compare against known issues from real audits.
Available Tools
mcp__solodit__search_findings
Primary search. Supports keywords, severity, firms, tags, language, protocol, time period, sorting, and advanced filters.
mcp__solodit__get_finding
Get full details for a specific finding by Solodit URL or slug.
mcp__solodit__get_filter_options
Discover valid filter values (firms, tags, categories, languages). Call this first if unsure what values to use.
When to Use
- Reviewing a vulnerability: Search for similar findings to check if it's a known pattern
- Auditing a protocol: Search by protocol category, language, or tags relevant to the codebase
- Researching a bug class: Search by tags (e.g., "Reentrancy", "Oracle") to find real examples
- Checking prior art: Before reporting a finding, search for similar issues to reference
- Studying an auditor: Use
advanced_filters.userto find a specific researcher's findings
Usage Patterns
Find similar issues
search_findings(keywords="oracle price manipulation", severity=["HIGH", "MEDIUM"], sort_by="Quality")
Research by firm
search_findings(firms=["Sherlock"], severity=["HIGH"], reported="90")
Explore a vulnerability tag
search_findings(tags=["Reentrancy", "Flash Loan"], severity=["HIGH"], sort_by="Quality")
Protocol-specific research
search_findings(protocol="Uniswap", severity=["HIGH", "MEDIUM"])
Language-specific search
search_findings(keywords="reentrancy", language="Solidity", sort_by="Quality")
High-quality solo findings (likely novel)
search_findings(
tags=["Oracle"],
advanced_filters={ quality_score: 4, max_finders: 1 }
)
Auditor research
search_findings(advanced_filters={ user: "0x52" }, severity=["HIGH"])
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 · 99 lines · 33 tokens per session scan A d1f3e64c2c62
solodit is a skill published in the GitHub repository marchev/claudit (157 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 807 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…