Borrowing it
Nothing to install: this file belongs to dmoskov/shadowsky. 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/dmoskov/shadowsky/main/CLAUDE.mdgit clone --depth 1 https://github.com/dmoskov/shadowskyWrote 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/dmoskov/shadowsky/claude-md)<a href="https://agentmods.dev/instructions/dmoskov/shadowsky/claude-md"><img src="https://agentmods.dev/badge/instructions/dmoskov/shadowsky/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/dmoskov/shadowsky/claude-md"><img src="https://agentmods.dev/badge/instructions/dmoskov/shadowsky/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.01176 | $0.01176 |
| Opus 5.5 | $0.00470 | $0.00470 |
| Sonnet 5.5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
shadowsky 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Universal Instructions
See: /Users/moskov/Code/CLAUDE.md for universal coding standards
Project: BSKY
Overview
This is the CLAUDE.md file for your project. Add project-specific instructions here.
Git Workflow
Branch Strategy
main— Development/staging branch. All feature work and fixes land here first. Auto-deploys tomain.asphodel.is.prod— Production branch. Deploys the web app (includingpublic/static files like OAuth client metadata). Auto-deploys toasphodel.is.task/*— Feature/task branches created frommain.
To deploy to production: merge main into prod and push. The prod branch auto-deploys to asphodel.is (production); main auto-deploys to main.asphodel.is (staging).
Rules
- NO automatic commits or pushes: Never run
git commitorgit pushautomatically. Always wait for explicit user approval before committing or pushing changes. - Show the user what changes would be committed and let them decide when to commit and push.
- ALWAYS run formatting checks before pushing: Before pushing to any branch, run
npm run test:formatto check for formatting issues. If there are issues, runnpm run fix:formatto fix them automatically.
Using the Push Script
A push script is available at scripts/push.sh that automatically runs pre-push checks:
# Basic usage (pushes to current branch)
./scripts/push.sh
# Push to specific branch
./scripts/push.sh origin feature-branch
# Force push (use with caution)
./scripts/push.sh --force
# Push with any git push arguments
./scripts/push.sh --set-upstream origin my-branch
The push script will:
- Check for uncommitted changes
- Run
npm run test:formatto check code formatting - Run
npm run buildto ensure the project builds successfully - Only push if all checks pass
If formatting issues are found, the script will suggest running npm run fix:format to fix them automatically.
UI Design Preferences
- No headers in feed views: Don't add title/description headers at the top of feed components. The user prefers a clean, header-free interface.
- Feed views should start directly with the content or feed selection controls.
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.
- 1mo ago First seen · 105 lines · 1,176 tokens per session scan A b5f42c265ee8
shadowsky CLAUDE.md is an instructions file published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed 1mo ago), licensed MIT. It adds 1,176 tokens to every session, about $0.0047 per session on Opus 5.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-09-01.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.