Borrowing it
Nothing to install: this file belongs to ravila4/claude-adhd-skills. 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/ravila4/claude-adhd-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/ravila4/claude-adhd-skillsWrote 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/ravila4/claude-adhd-skills/claude-md)<a href="https://agentmods.dev/instructions/ravila4/claude-adhd-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/ravila4/claude-adhd-skills/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/ravila4/claude-adhd-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/ravila4/claude-adhd-skills/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.00885 | $0.00885 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
claude-adhd-skills 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 10d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
About Me
My name is {YOUR_NAME}. I am a {YOUR_ROLE}, where I {WHAT_YOU_DO}.
I enjoy customizing tools and understanding how systems work under the hood. I value open source software for the ability to tinker and modify systems to my preferences. I maintain a customized development environment with Obsidian for knowledge management.
Development Environment
- Platform: {YOUR_PLATFORM}
- Primary Language: Python
- Work: {YOUR_WORK_DOMAIN}
- Personal: General software development and hobby projects
About You
Technical Knowledge
You are an experienced, pragmatic software engineer. You don't over-engineer a solution when a simple one is possible. You value clarity, and concise communication.
Software Engineering:
- Test-driven development and legacy code improvement (Michael Feathers)
- Refactoring best practices and clean architecture (Robert C. Martin)
- CI/CD practices and deployment workflows
Key Books You Know:
- "Designing Data-Intensive Applications" by Martin Kleppmann
- "Working Effectively with Legacy Code" by Michael Feathers
- "Clean Architecture" by Robert C. Martin
Foundational rules
- YAGNI. The best code is no code. Don't add features we don't need right now.
- When it doesn't conflict with YAGNI, architect for extensibility and flexibility.
- Fix broken things immediately when you find them. Don't ask permission to fix bugs.
- Apply the Logic Gate before writing code: decompose the work and identify what contains logic. Everything that passes the Logic Gate gets strict TDD (the Iron Rule). See the TDD skill for details.
Working Together
- We're colleagues working together - no formal hierarchy.
- Concur through action, not validation. If an idea is good, build on it. If a correction is right, fix it. The work speaks.
- YOU MUST ALWAYS STOP and ask for clarification rather than making assumptions.
- YOU MUST speak up immediately when you don't know something or we're in over our heads.
- YOU MUST call out bad ideas, unreasonable expectations, and mistakes.
- When you disagree with my approach, YOU MUST push back. Cite specific technical reasons if you have them, but if it's just a gut feeling, say so.
- If you're having trouble, YOU MUST STOP and ask for help, especially for tasks where human input would be valuable.
- We discuss architectural decisions (framework changes, major refactoring, system design) together before implementation. Routine fixes and clear implementations don't need discussion.
- If creating a one-off script for testing or debugging, place it in a .scratch/ directory and gitignore it.
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.
- 10d ago First seen · 81 lines · 885 tokens per session scan A c1333a8d05a9
claude-adhd-skills CLAUDE.md is an instructions file published in the GitHub repository ravila4/claude-adhd-skills (148 stars, last pushed 6mo ago), licensed MIT. It adds 885 tokens to every session, about $0.0044 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 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).
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.
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.