Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/doccker/cc-use-exp/generalgit clone --depth 1 https://github.com/doccker/cc-use-expWrote 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/doccker/cc-use-exp/general)<a href="https://agentmods.dev/instructions/doccker/cc-use-exp/general"><img src="https://agentmods.dev/badge/instructions/doccker/cc-use-exp/general.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 | $0.00163 | $0.00163 |
| Opus 5 | $0.00081 | $0.00081 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
cc-use-exp general.instructions.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 today.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 14 lines · 163 tokens per session scan A c45122c82eb8
cc-use-exp general.instructions.md is an instructions file published in the GitHub repository doccker/cc-use-exp (1,036 stars, last pushed 8d ago), with no licence file. It adds 163 tokens to every session, about $0.0008 per session on Opus 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-03.
Other instructions, from other repositories
mantis AGENTS.md
AGENTS.md instructions for google/mantis, covering agent rules, before committing, verbatim blocks, reference files and extraction criteria.
ai-driven-development AGENTS.md
AGENTS.md instructions for CodeAlive-AI/ai-driven-development, covering ai-driven development — development guide, git publishing defaults, when to create tags and releases, requires a new tag/release and does not require a new tag/release.
kaos-control AGENTS.md
AGENTS.md instructions for kcsinclair/kaos-control, covering claude.md, what this is, authoritative spec, repository layout and build & run.
ai-driven-development CLAUDE.md
Claude Code instructions for CodeAlive-AI/ai-driven-development, a project described as: Practices, protocols, and skills for AI-driven software development. Skills and safety hooks for Claude Code, Codex, OpenCode, Cursor, Antigravity, and any agent supporting the Agent Skills standard.
100xprism AGENTS.md
AGENTS.md instructions for rajitsaha/100xprism, covering agents.md, what this repo is, the golden rule, module shape and retention: what earns a permanent slot.
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).