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 skills/florianbruniaux/ctxharness/eval-rulesnpx skills add FlorianBruniaux/ctxharness --skill eval-rulesgit clone --depth 1 https://github.com/FlorianBruniaux/ctxharnessWrote 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/skills/florianbruniaux/ctxharness/eval-rules)<a href="https://agentmods.dev/skills/florianbruniaux/ctxharness/eval-rules"><img src="https://agentmods.dev/badge/skills/florianbruniaux/ctxharness/eval-rules.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.00077 | $0.01401 |
| Opus 5 | $0.00039 | $0.00700 |
| Sonnet 5 | $0.00015 | $0.00280 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
eval-rules 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules Evaluator
Discover all rule files, validate their structure and glob patterns against the real project, then run an interactive session to confirm (or improve) each rule.
The goal is not just to score — it is to leave the rules directory in better shape than it was.
When to Use
- First time writing
.claude/rules/files (validate before committing) - A rule seems to never trigger, or fires on every file
- Migrating
@imports from CLAUDE.md to path-scoped rules - Periodic hygiene: "are these rules still relevant to how we work?"
- Before shipping ctxharness as a new project to users
Key Concepts
| Mechanism | When it loads | Notes |
|---|---|---|
@file in CLAUDE.md |
Session start, always | Even inside a conditional sentence |
No paths: in rule |
Session start, always | Same cost as @import |
paths: frontmatter |
When Claude reads a matching file | Trigger = Read tool, not Write |
The paths: field is the main lever for keeping rules contextual. An always-on rule with 80 lines loads on every session even if you're fixing a typo in README.md.
Scoring Criteria (12 pts per rule)
| # | Criterion | Max | What is checked |
|---|---|---|---|
| 1 | frontmatter block | 1 | File has YAML frontmatter (--- delimited) |
| 2 | paths: field | 2 | Present (1pt) + at least one pattern listed (1pt) |
| 3 | pattern validity | 3 | Each pattern matches ≥1 file in project (up to 3 patterns checked) |
| 4 | scope | 2 | Not dead (≥1 match) + not too broad (<30% of project source files) |
| 5 | content quality | 3 | Has clear header/title (1pt) + rules are specific/actionable (1pt) + under 150 lines (1pt) |
| Bonus | focus | +1 | Under 15 rules in file |
Thresholds:
- ✅ Good: ≥10/12 (≥83%)
- ⚠️ Needs work: 7–9/12 (58–82%)
- ❌ Fix: <7/12 (<58%)
Always-on rules (no paths: field): skip criteria 2, 3, 4. Score on 5 pts max. Flag with 🔵 and go through the interactive step to decide if scoping is needed.
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 · 149 lines · 77 tokens per session scan A 2fa02701cd89
eval-rules is a skill published in the GitHub repository FlorianBruniaux/ctxharness (21 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,401 once invoked, about $0.0004 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 skills, from other repositories
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup/decline and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.
claude-context-improver
Audit and improve the Claude Code context layer — CLAUDE.md guidance files, .claude/rules/ path-scoped rules, and companion codemap.md navigation maps — against Claude 5 context-engineering rules (judgement over rules, progressive disclosure, no cross-layer conflicts). Asks whether to optimize the current repository…
onboarding-index
Discover CEP-managed content already present in a target repo (What/How layer docs, compiled guidelines, context packages, decision ledger) via existence checks against layout-slots-registry.yaml-resolved paths, then write one canonical root AGENTS.md onboarding index plus thin per-tool pointer stubs…
autoscaffold-content
Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module…
ai-project-starter
Use when the user wants to prepare project-specific context engineering documents, AI coding agent instruction files, project starter Markdown files, vibe coding guardrails, PRD/TDD/architecture/security/testing docs, AGENTS.md/CLAUDE.md/Cursor/Windsurf/Continue/Copilot context files, or a complete AI-coding-ready…
sourcebook-lookup
Searches internal AI documentation about team systems, processes, conventions, architectural decisions, and API references. Use this skill whenever working with service code, build pipelines, deployments, backend services, or infrastructure code. Also use before suggesting architectural approaches to check if a…