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/numman-ali/cc-mirror/agents-mdgit clone --depth 1 https://github.com/numman-ali/cc-mirrorWrote 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/numman-ali/cc-mirror/agents-md)<a href="https://agentmods.dev/instructions/numman-ali/cc-mirror/agents-md"><img src="https://agentmods.dev/badge/instructions/numman-ali/cc-mirror/agents-md.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.02792 | $0.02792 |
| Opus 5 | $0.01396 | $0.01396 |
| Sonnet 5 | $0.00558 | $0.00558 |
| Haiku 4.5 | $0.00279 | $0.00279 |
Grade A, and why
cc-mirror AGENTS.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 4d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure
src/
├── cli/ # CLI entrypoint and commands
│ ├── index.ts # Main CLI entry
│ ├── commands/ # create, update, remove, doctor, etc.
│ └── args.ts # Argument parsing
├── tui/ # Ink-based TUI wizard
│ ├── app.tsx # Main TUI application
│ ├── screens/ # Individual screen components
│ ├── components/ # Reusable UI components
│ ├── hooks/ # React hooks for business logic
│ ├── state/ # State types and management
│ └── router/ # Screen navigation
├── core/ # Core variant management
│ ├── index.ts # Public API (createVariant, updateVariant, etc.)
│ ├── variant-builder/ # Step-based variant creation
│ │ ├── VariantBuilder.ts
│ │ ├── VariantUpdater.ts
│ │ ├── steps/ # Build steps (PrepareDirectories, InstallNative, etc.)
│ │ └── update-steps/ # Update steps
│ ├── prompt-pack/ # System prompt overlays
│ │ ├── providers/ # Per-provider overlays (zai.ts, minimax.ts)
│ │ ├── overlays.ts # Overlay resolution
│ │ └── targets.ts # Target file mapping
│ └── *.ts # Utils (paths, fs, tweakcc, skills, etc.)
├── providers/ # Provider templates
│ └── index.ts # Provider definitions and defaults
├── brands/ # TweakCC brand presets
│ ├── index.ts # Brand resolution
│ ├── types.ts # TweakCC config types
│ ├── zai.ts # Z.ai theme + blocked tools
│ ├── minimax.ts # MiniMax theme + blocked tools
│ └── *.ts # Other brand configs
test/ # Node test runner tests
├── e2e/ # End-to-end tests
├── tui/ # TUI component tests
├── unit/ # Unit tests
└── helpers/ # Test utilities
repos/ # Upstream reference copies (vendor data, history)
├── anthropic-claude-code-*/ # Claude Code versions for comparison/reference
├── claude-code-system-prompts/ # System prompt changelog and sources
└── tweakcc/ # TweakCC repo (prompt patching tool)
notes/ # Research notes and deep dive documentation
├── CLI-VERSIONS.md # Version comparison notes
├── *-DEEP-DIVE.md # Feature research and analysis
└── RECONSTRUCTION-LEDGER.md # Project state and decisions
docs/ # User documentation
dist/ # Build output (generated)
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.
- 4d ago First seen · 297 lines · 2,792 tokens per session scan A 0394d1f6d5ce
cc-mirror AGENTS.md is an instructions file published in the GitHub repository numman-ali/cc-mirror (2,260 stars, last pushed 3mo ago), licensed MIT. It adds 2,792 tokens to every session, about $0.0140 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-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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.