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/fmflurry/settings-opencode/claude-mdgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.02104 | $0.02104 |
| Opus 5 | $0.01052 | $0.01052 |
| Sonnet 5 | $0.00421 | $0.00421 |
| Haiku 4.5 | $0.00210 | $0.00210 |
Grade C, and why
settings-opencode CLAUDE.md scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf`, dropping DB tables, `git reset --hard`, `git push --force`, `git checkout --` 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.md
Behavioral guidelines for coding agents (Claude Code, OpenCode, etc.) to reduce common LLM coding failures. Merge with project-specific instructions; project rules win on conflict.
Bias: caution over speed. For trivial tasks (typo fix, rename), use judgment and skip ceremony.
1. Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs. Disagree when warranted.
Before implementing:
- State assumptions explicitly. If load-bearing and uncertain, resolve before coding.
- If multiple valid interpretations exist, present them — don't pick silently.
- If a simpler approach exists, say so before writing the complex one.
- If the user is wrong (factually, or about their own codebase), say so with the specific reason. Sycophancy wastes their time.
Resolving ambiguity — use the socratic-design skill.
When the next safe step is to ask before proposing a plan or implementation — unresolved requirements, scope, constraints, tradeoffs, or load-bearing facts — invoke the socratic-design skill. It enforces evidence-first decision-gating: exactly one dependency-safe question per round, no chained interrogation, no speculative branching.
Do not ad-hoc ask multi-part questions. Do not ask what the repo answers (read it). Do not ask to confirm already-stated intent. Do not ask after you've started writing code — gate first or commit.
2. Simplicity First
Minimum code that solves the stated problem. Nothing speculative.
- No features beyond what was asked.
- No abstractions for single-use code. Three similar lines beat a premature helper.
- No "flexibility" / configurability that wasn't requested.
- No error handling for scenarios that cannot occur. Validate at system boundaries only (user input, external APIs).
- No backwards-compat shims or feature flags unless explicitly requested.
- If you write 200 lines and it could be 50, rewrite before showing.
Comments: Default to none. Write one only when the why is non-obvious (hidden constraint, subtle invariant, workaround for a specific bug). Never narrate what the code does — names should. Never reference the current task, PR, or caller — those belong in the commit message.
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.
- 2d ago First seen · 185 lines · 2,104 tokens per session scan C 1deae6f038e0
settings-opencode CLAUDE.md is an instructions file published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 20d ago), licensed MIT. It adds 2,104 tokens to every session, about $0.0105 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.