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/blackwell-systems/gcf/claude-mdgit clone --depth 1 https://github.com/blackwell-systems/gcfWrote 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/blackwell-systems/gcf/claude-md)<a href="https://agentmods.dev/instructions/blackwell-systems/gcf/claude-md"><img src="https://agentmods.dev/badge/instructions/blackwell-systems/gcf/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 | $0.02473 | $0.02473 |
| Opus 5 | $0.01236 | $0.01236 |
| Sonnet 5 | $0.00495 | $0.00495 |
| Haiku 4.5 | $0.00247 | $0.00247 |
Grade A, and why
gcf 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCF Project Instructions
Eval Data Update Procedure
When new comprehension or generation eval runs are added, the following files must be updated. Do all of them in a single pass. Do not wait to be asked.
CRITICAL: Never copy numbers from existing docs or memory. Always recompute from the raw log files. Stale numbers have propagated before because averages were copied from one surface to another instead of recomputed. The log files in eval/results/comprehension/ are the single source of truth.
Step 0: Verify from raw logs
Before updating anything, recompute all headline numbers from the raw log files:
# Run this from eval/results/comprehension/
# Parse ALL comprehension-13q-*.log AND any .txt files with comprehension data
# Extract per-format scores, group by model, compute per-model averages
# Then average the per-model averages (NOT the per-run averages)
# This is the "average of model averages" methodology
Known naming inconsistencies in log files:
- Some runs use hyphens (
gemini-2.5-flash), others don't (gemini25flash). Same model. - Some runs are
.txtnot.log(e.g.,haiku-4.5-run2.txt). Still valid data. - Opus has
run2but norun1comprehension log. Only 1 adversarial run exists. - Always glob for both
comprehension-13q-*AND any other.txtfiles with comprehension data.
Step 1: Record the run
- Save log file to
eval/results/comprehension/oreval/results/generation/with standard naming:comprehension-13q-{model}-run{N}-{date}.logorgeneration-{model}-run{N}-{date}.log
Step 2: Update SUMMARY (this repo)
eval/results/SUMMARY.md: Add to "All runs" table, update "Averages by model" table, update file listing. If failure taxonomy counts change, update those too.
Step 3: Recalculate headline numbers
After updating the SUMMARY, recalculate FROM RAW LOGS (not from existing docs):
- Overall GCF average: average of per-model averages (not average of all runs; models with more runs should not be overweighted)
- Run count: total comprehension runs, total generation runs
- Win/tie/loss record: GCF vs TOON across all comprehension runs
- Total evaluations: (comprehension runs x 13 questions x 3 formats) + (generation runs x 5 sizes x 3 formats)
- Model count: count of distinct models (combine same-model runs with different naming)
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 · 174 lines · 2,473 tokens per session scan A a06fcf6cb33e
gcf CLAUDE.md is an instructions file published in the GitHub repository blackwell-systems/gcf (45 stars, last pushed today), licensed MIT. It adds 2,473 tokens to every session, about $0.0124 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
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
seekstone CLAUDE.md
Claude Code instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
mistral-mcp CLAUDE.md
Instructions for Swih/mistral-mcp, covering claude.md — mistral-mcp, 1. identité du projet, 2. règles dures (ne pas transgresser), 3. layout & responsabilités and 4. conventions de code.
pfsense-mcp-server AGENTS.md
AGENTS.md instructions for night4me/pfsense-mcp-server, covering pfsense mcp server, architecture and security, development workflow, long-running validation and test parallelism.
backlog-mcp AGENTS.md
AGENTS.md instructions for gkoreli/backlog-mcp, covering agents.md — guidelines for ai agents working in backlog-mcp, testing, philosophy, how it works and test locations.
trello-mcp AGENTS.md
AGENTS.md instructions for enthouan/trello-mcp, covering agents.md, project summary, hard constraints, runtime and package manager and common commands.