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/acartine/foolery/claude-mdgit clone --depth 1 https://github.com/acartine/fooleryWrote 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/acartine/foolery/claude-md)<a href="https://agentmods.dev/instructions/acartine/foolery/claude-md"><img src="https://agentmods.dev/badge/instructions/acartine/foolery/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.02131 | $0.02131 |
| Opus 5 | $0.01066 | $0.01066 |
| Sonnet 5 | $0.00426 | $0.00426 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
foolery 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Codex Configuration
When using Codex CLI in this project:
- approval_policy:
never(autonomous mode for routine work) - model_reasoning_effort:
xhigh(complex codebase, needs deep reasoning)
Override with: codex -c approval_policy=ask or codex -c model_reasoning_effort=medium as needed.
Repository Overrides
These repo-level rules are mandatory for all agents working in this project:
- Use Knots (
kno) as the only work-tracking system. - Do not use any alternate tracker in this repository.
- Never move knots to terminal states unless the user explicitly instructs you.
- Never use a PR workflow unless the user explicitly instructs you to use PRs.
Git Worktree Policy (Hard Override)
This repository supports parallel agent work using Git worktrees.
- Do implementation work in a dedicated Git worktree.
- Worktrees may use short-lived local branches for isolation.
- Final integrated changes must be pushed to remote
main(origin/main). - Do not require reviews or pull requests unless the user explicitly requests them.
Worktree Dependency Bootstrap
Each Git worktree is a separate checkout and does not share node_modules.
- After creating or switching to a worktree, run:
bun install --frozen-lockfile - Run dependency install before lint, typecheck, test, or build commands.
- Prefer
bun run <script>overbunx <tool>so plugins resolve from local project dependencies. - If
node_modulesis missing in the worktree, treat lint/typecheck results as invalid until install completes.
Code Style Constraints
- File length: max 500 lines per source file
- Function length: max 100 lines per function
- Line length: max 100 columns per line
These are enforced by ESLint (max-lines, max-lines-per-function, max-len).
kno Workflows Are Authoritative
kno .loom workflows are the single source of truth; Foolery TS must never override, extend, or post-process them (no synthetic transitions, no parallel canonical graph). Correction actions that skip gates must be named as such and invoke kno idiomatically with force: true (see KnotsBackend.close()); details in docs/DEVELOPING.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 · 151 lines · 2,131 tokens per session scan A 5aefa9f618a1
foolery CLAUDE.md is an instructions file published in the GitHub repository acartine/foolery (54 stars, last pushed 1mo ago), licensed MIT. It adds 2,131 tokens to every session, about $0.0107 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
AllBeads CLAUDE.md
Instructions for thrashr888/AllBeads, covering claude.md, project overview, what allbeads does, current state (v0.2.0) and rust development commands.
scaffold AGENTS.md
Instructions for zigrivers/scaffold, covering agent instructions, quick reference, scaffold releases and landing the plane (session completion).
flow AGENTS.md
Instructions for cofin/flow: Flow is a toolkit for context-driven development. It has no flow executable; invoke the Flow skill or a /flow: command.
flow CLAUDE.md
Instructions for cofin/flow: Flow is a skill, not a CLI. In repositories with .agents/, invoke the Flow skill or a /flow: command.
looper_rust AGENTS.md
Instructions for quangdang46/looper_rust, covering looper rust — ai agent guidelines, build, test, lint and workspace members.
bd-explore GEMINI.md
Gemini CLI instructions for halaprix/bd-explore, covering gemini.md - gemini / antigravity guide for bd-explore, context & guidelines, running verification tests and structure.