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/sgharlow/ai-control-framework/claude-mdgit clone --depth 1 https://github.com/sgharlow/ai-control-frameworkWrote 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/sgharlow/ai-control-framework/claude-md)<a href="https://agentmods.dev/instructions/sgharlow/ai-control-framework/claude-md"><img src="https://agentmods.dev/badge/instructions/sgharlow/ai-control-framework/claude-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.1 | $0.01577 | $0.01577 |
| Opus 5 | $0.00788 | $0.00788 |
| Sonnet 5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
ai-control-framework 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 5d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE CODE CONFIGURATION
AI Agent Operating Instructions - READ FIRST
FRAMEWORK STATUS (v2.0) — verified 2026-07-18
- Validation suite: 28/28 passing (
validate-framework.sh; in CI) - Dashboard tests: 14/14 vitest (in CI, Node 20/22)
- MCP Server: builds clean (
tsc; in CI, Node 20/22). The ad-hoctests/*.jstool scripts require a live stdio MCP client and are NOT in CI. - DRS Components: All 13 implemented with correct weights
- Retired claim: an earlier "136/136 integration tests" status referenced
framework-integration-test.sh, which does not exist in the repo. Do not restate that number. - Dogfood DRS: 27/100 self-score (see root README for methodology honesty)
⚠️ CRITICAL: IMPLEMENTATION REQUIRED
This framework uses a "Specification-First, Implementation-Flexible" approach.
The framework provides:
- SPECIFICATIONS of what to check (
ai-framework/specs/) - REFERENCE IMPLEMENTATIONS as examples (
ai-framework/reference/) - MANUAL CHECKLISTS as fallback (
ai-framework/reference/checklists/)
YOU MUST:
- Read
ai-framework/IMPLEMENTATION-GUIDE.mdFIRST - Choose or adapt an implementation that works in your environment
- Use the specifications to understand WHAT to check
- Use the references to understand HOW to check
- Fall back to manual checklists if scripts fail
The scripts are NOT magic - they are EXAMPLES that need adaptation!
MANDATORY SESSION START PROCEDURE
-
Load Framework Files (Every Session)
- Read
ai-framework/templates/code.md- Current session state - Read
ai-framework/templates/orchestration.md- Control rules - Read
ai-framework/templates/patterns.md- Implementation patterns - Read
ai-framework/IMPLEMENTATION-GUIDE.md- How to run checks - Perform safety checks per
ai-framework/specs/guidelines
- Read
-
Select Pattern Before Coding
- NO implementation without pattern selection
- Match task to PATTERN-XXX from patterns.md
- Document pattern choice in templates/code.md
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.
- 5d ago First seen · 185 lines · 1,577 tokens per session scan A 0197a6712b77
ai-control-framework CLAUDE.md is an instructions file published in the GitHub repository sgharlow/ai-control-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,577 tokens to every session, about $0.0079 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-31.
Other instructions, from other repositories
specops CLAUDE.md
Instructions for sanmak/specops, covering claude.md, what is specops, build & validate commands, run all tests (single command) and generate for a single platform.
skillfoundry copilot-instructions.md
Copilot instructions for samibs/skillfoundry, covering github copilot — skillfoundry project instructions, identity, non-negotiable rules, code quality and security.
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.
plan-forge blazor-fluent-ui.instructions.md
Blazor Server + Microsoft Fluent UI patterns — component layering, state, lifecycle, accessibility. Auto-loads when editing .razor / .razor.cs files.
plan-forge copilot-instructions.md
Copilot instructions for srnichols/plan-forge, covering instructions for copilot, architecture principles, core principles (non-negotiable), cost estimates and talking to forge-master.