Borrowing it
Nothing to install: this file belongs to 45ck/skill-harness. 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/45ck/skill-harness/main/CLAUDE.mdgit clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/45ck/skill-harness/claude-md)<a href="https://agentmods.dev/instructions/45ck/skill-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/45ck/skill-harness/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/45ck/skill-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/45ck/skill-harness/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.00958 | $0.00958 |
| Opus 5.5 | $0.00383 | $0.00383 |
| Sonnet 5.5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
skill-harness 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Harness
Use the narrowest specialist agent that can own the work end to end. Treat this repo as the suite entrypoint and project setup repo for the 45ck stack, including embedded packs under packs/.
This is maintainer and agent operating guidance. Public contributors should start with CONTRIBUTING.md, SUPPORT.md, and SECURITY.md; fork-based contributors do not need Beads locally and should use pull requests instead of direct pushes.
UML-First Developer Artifacts
- Auto-detect model impact for every engineering change. When code, API, workflow, dependency, deployment, UI structure, or agent behavior changes, update the relevant model source or record why no model change is needed.
- Fresh developer-artifact setups use
--modeling-mode auto, which resolves touml-firstfor new repos and preserves existing repos. Use--modeling-mode off|baseline|uml-firstor--skip-modelingonly when that is intentional. - Keep canonical UML/UWE/C4/evidence model sources in repo-relative text files. Prefer
docs/artifacts/source/models/when no better domain docs path exists. - Keep
docs/artifacts/source/models/model-inventory.mdanddocs/artifacts/artifacts.manifest.jsoncurrent with model ids, owners, methods, source paths, evidence, and generated review surfaces. - Human model artifacts belong in static HTML under
generated/review/models/. Generate them withnode scripts/generate-model-review.mjs; validate withnode scripts/check-model-artifact-policy.mjsandnode scripts/check-artifact-html-policy.mjs. - Human-facing discovery, planning, research, product, business, data, and UX artifacts belong in source-backed infographic HTML under
generated/review/<family>/. Create the canonical source first, mark the manifest entryreviewRequired: true, generate withnode scripts/generate-artifact-review.mjs, then surface/open the HTML review page. - Default generated review interaction is CSS-only: radio tabs, details/summary, anchor navigation, and inline SVG states. Do not add inline JavaScript; the reviewed inline-JS lane is reserved until manifest-aware checker and CSP support are implemented.
- Open generated HTML in the best available human review surface. In Codex app, prefer the Browser plugin for local HTML. In Claude desktop, prefer the built-in browser or preview. In CLI-only contexts, use
node scripts/open-artifact-review.mjsto open the system default browser or print the file URL in headless/CI contexts. - Use
node scripts/open-artifact-review.mjs --json --printwhen a host workflow needs the resolved review target and preferred open action before choosing a browser, preview, or local HTTP fallback. - Treat generated HTML, SVG, PNG, screenshots, and comparison pages as review surfaces only. Canonical truth stays in source artifacts and model diffs.
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 · 38 lines · 958 tokens per session scan A d71314cbe920
skill-harness CLAUDE.md is an instructions file published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 4mo ago), licensed MIT. It adds 958 tokens to every session, about $0.0038 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-08-30.
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.