Borrowing it
Nothing to install: this file belongs to umputun/cc-thingz. 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/umputun/cc-thingz/master/CLAUDE.mdgit clone --depth 1 https://github.com/umputun/cc-thingzWrote 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/umputun/cc-thingz/claude-md)<a href="https://agentmods.dev/instructions/umputun/cc-thingz/claude-md"><img src="https://agentmods.dev/badge/instructions/umputun/cc-thingz/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/umputun/cc-thingz/claude-md"><img src="https://agentmods.dev/badge/instructions/umputun/cc-thingz/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.01413 | $0.01413 |
| Opus 5.5 | $0.00565 | $0.00565 |
| Sonnet 5.5 | $0.00283 | $0.00283 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
cc-thingz 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Purpose
Things to make Claude Code even better — hooks, skills, and commands, organized as a marketplace of independent plugins.
Key Rules
- README.md must be kept up to date — whenever a new component, script, or configuration is added, update README.md with a description of what it does and how to use it.
- Content is MIT-licensed.
- This is a personal project by Umputun (GitHub).
- No personal configuration — scripts and configs must be generic and not contain hardcoded personal paths, editor preferences, or machine-specific settings. Use environment variables (e.g.,
$EDITOR) for user-specific values. - Self-contained documentation — do not reference external custom skills, actions, or configurations that exist only in a user's personal Claude Code setup. All documentation must refer only to what exists in this repository.
Conventions
- Hook scripts use
${CLAUDE_PLUGIN_ROOT}for path resolution when running as a plugin. The plugin system copies files to a cache location during install, so absolute/relative paths won't work. - Manual install instructions are kept in README.md as a fallback for users who prefer direct setup.
- Versioning — each plugin has its own
versioninplugins/<name>/.claude-plugin/plugin.json. Bump independently per plugin. Use semver: patch for bug fixes, minor for new components, major for breaking changes. Bump triggers on any change to bundled plugin content — prompts, agents, references (e.g.,usage.md), scripts, commands, hooks — not just.claude-plugin/files. Anything shipped to consumers via the plugin is a release artifact. - Changelog: when bumping a plugin version, update
CHANGELOG.mdin the same change. Version headings use the plugin name and plugin version (e.g.,## planning v3.7.1 - YYYY-MM-DD), not tags. Keep entries grouped like the changelog style: New Features, Improvements, Bug Fixes, Other. - Cross-references — when skills reference other skills within the same plugin, use the plugin name prefix (e.g.,
/review:writing-style). When referencing skills in other plugins, use that plugin's name (e.g.,/planning:make).
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 · 66 lines · 1,413 tokens per session scan A f7d13dcda832
cc-thingz CLAUDE.md is an instructions file published in the GitHub repository umputun/cc-thingz (490 stars, last pushed 2d ago), licensed MIT. It adds 1,413 tokens to every session, about $0.0057 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.