Borrowing it
Nothing to install: this file belongs to paultyng/skill-issue. 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/paultyng/skill-issue/main/CLAUDE.mdgit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/claude-md)<a href="https://agentmods.dev/instructions/paultyng/skill-issue/claude-md"><img src="https://agentmods.dev/badge/instructions/paultyng/skill-issue/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/paultyng/skill-issue/claude-md"><img src="https://agentmods.dev/badge/instructions/paultyng/skill-issue/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.00446 | $0.00446 |
| Opus 5.5 | $0.00178 | $0.00178 |
| Sonnet 5.5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade B, and why
skill-issue CLAUDE.md scanned grade B 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `settings.merge.json` — Curated keys merged into `~/.claude/settings.json` (model, permissions, hooks, plugins). What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Repo Is
Personal user-level Claude Code skills, rules, and settings. The canonical clone (this repo) is the source of truth; ~/.claude/ is populated by ./install.sh.
Repository Structure
skills/— Multi-step agent workflows (SKILL.md per directory). See.claude/rules/skill-authoring.mdfor conventions.rules/— Behavioral rules that auto-load every session. See.claude/rules/rule-authoring.mdfor conventions.scripts/— Shell scripts including statusline.settings.merge.json— Curated keys merged into~/.claude/settings.json(model, permissions, hooks, plugins).install.sh— Install/sync script.
Creating Skills and Rules
Use /create-skill and /create-rule respectively. Do not author SKILL.md or rule files from scratch.
Sync workflow
~/.claude/is populated by./install.shrunning from this canonical clone.- Edits to
skills/,rules/,scripts/, and top-level files in this repo flow into~/.claude/on each install. - Personal/local skills/rules/scripts in
~/.claude/are preserved (never deleted). settings.jsonis jq-merged: specific keys (model,effortLevel,statusLine,enabledPlugins,extraKnownMarketplaces,permissions.allow,hooks) flow fromsettings.merge.json; everything else stays user-local.
Portability
This repo must remain portable and free of company-specific content:
- No internal URLs, proprietary tool names, or org-specific workflows in skills, rules, or settings.
- Skills that need org-specific context should read it from project-level
CLAUDE.md,REVIEW.md, or.claude/rules/at runtime. - MCP tool references use fully qualified names (
ServerName:tool_name).
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.
- 2mo ago First seen · 35 lines · 446 tokens per session scan B 7108a9a6f82a
skill-issue CLAUDE.md is an instructions file published in the GitHub repository paultyng/skill-issue (8 stars, last pushed 13d ago), licensed MIT. It adds 446 tokens to every session, about $0.0018 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.