Borrowing it
Nothing to install: this file belongs to srnichols/plan-forge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/srnichols/plan-forge/master/.github/instructions/context-fuel.instructions.mdgit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/context-fuel)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/context-fuel"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/context-fuel/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/context-fuel"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/context-fuel.svg" alt="Reviewed on agentmods" width="80" 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.00767 | $0.00767 |
| Opus 5.5 | $0.00307 | $0.00307 |
| Sonnet 5.5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
plan-forge context-fuel.instructions.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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Fuel
Context is what fuels good agent output. Running low starves quality.
When to Load What
| Situation | Action |
|---|---|
| Session start | Call forge_capabilities once — gets the full surface (tools, skills, config, extensions) in one call instead of reading multiple files |
| Working on database code | Prioritize database.instructions.md, security.instructions.md — read these first, reference others only when needed |
| Working on API endpoints | Prioritize api-patterns.instructions.md, auth.instructions.md, errorhandling.instructions.md |
| Working on tests | Prioritize testing.instructions.md — the test patterns and Temper Guards are more valuable than reviewing architecture rules |
| Executing a plan slice | Read the plan's Scope Contract and the specific slice — don't reload the full plan every slice |
| Context feels degraded | Stop and re-read architecture-principles.instructions.md — it's the universal baseline that anchors everything else |
Recognizing Context Degradation
You are losing context when:
- You repeat a mistake that a loaded instruction file already warns against
- You forget a constraint you acknowledged earlier in the session (naming convention, forbidden pattern, tech commitment)
- You make an architectural decision that contradicts the project's established patterns
- You suggest adding a dependency that the Project Principles explicitly forbid
- Your output quality drops noticeably — shorter explanations, missed edge cases, skipped validation
- You can't recall the Scope Contract for the current slice
What to Do When Context Degrades
- Re-read the active instruction files — not all of them, just the ones relevant to the current task
- Check Project Principles — re-read
docs/plans/PROJECT-PRINCIPLES.mdif it exists - Search memory — if OpenBrain is configured, run
search_thoughtsfor the current task context to recall prior decisions - Recommend a fresh session — Plan Forge uses 4 sessions for a reason. If context is severely degraded, suggest the user start a new session and hand off via the plan's status artifacts
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.
- 1mo ago First seen · 60 lines · 767 tokens per session scan A 9d8a0b910c48
plan-forge context-fuel.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 767 tokens to every session, about $0.0031 per session on Opus 5.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
vscode buildNext.instructions.md
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
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, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).