Borrowing it
Nothing to install: this file belongs to Osipchuk/agent-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/Osipchuk/agent-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/Osipchuk/agent-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/osipchuk/agent-skills/claude-md)<a href="https://agentmods.dev/instructions/osipchuk/agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/osipchuk/agent-skills/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.02329 | $0.02329 |
| Opus 5 | $0.01164 | $0.01164 |
| Sonnet 5 | $0.00466 | $0.00466 |
| Haiku 4.5 | $0.00233 | $0.00233 |
Grade A, and why
agent-skills 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Two install tracks.** Humans: `install.sh` (uvx/`uv tool install` from git). The agent path: the Claude Code plugin marketplace (`.claude-plugin/marketplace.json` → `/plugin install skills@askill`), which is the trus How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code working in this repo: how to work here first, then how the project is built. The working principles are adapted from Andrej Karpathy's skills CLAUDE.md (multica-ai/andrej-karpathy-skills); merge with anything more specific a task demands.
Tradeoff: these principles bias toward caution over speed. For a trivial task, use judgment.
Working principles
1. Think before coding
Don't assume, don't hide confusion, surface tradeoffs. State your assumptions; if several readings are possible, present them instead of silently picking one. If a simpler path exists, say so. If something is unclear, stop and name it — a clarifying question before the work beats a rewrite after it.
2. Simplicity first
Minimum code that solves the problem, nothing speculative. No abstraction for a single caller, no configurability nobody asked for, no error handling for impossible states. This repo already has a small, clean deterministic core — match that bar, don't gold-plate past it. If you wrote 200 lines and 50 would do, rewrite it.
3. Surgical changes
Touch only what the task needs. Don't "improve" adjacent code, comments, or formatting; don't refactor what isn't broken; match the surrounding style even if you'd write it differently. Remove only the imports/vars/functions your change orphaned — flag pre-existing dead code, don't delete it unasked. Every changed line should trace to the request.
4. Verify, don't assert
Turn the task into a check and loop until it passes. "Fix the bug" → write the failing test first, then make it pass. Before claiming done, actually run it: uv run pytest && uv run ruff check . && uv run mypy src from installer/. Generated artifacts (below) have their own check — regenerate and diff, don't eyeball.
Two repo-specific habits fall out of these:
- The deterministic Core is the product. Keep logic pure in
core/; isolate side effects (I/O, network, prompts) at the edges.cli.py/commands/only parse args and call Core; the human-vs-JSON decision lives inutils/output.py, not in commands. - Generated files are never hand-edited. Change the generator, run it, commit the output — see "Generated artifacts" below.
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 · 94 lines · 2,329 tokens per session scan A 20a9be25dd08
agent-skills CLAUDE.md is an instructions file published in the GitHub repository Osipchuk/agent-skills (5 stars, last pushed 27d ago), licensed MIT. It adds 2,329 tokens to every session, about $0.0116 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.