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/rpraharaj/forward-deployed-engineer/context-strategynpx skills add rpraharaj/forward-deployed-engineer --skill context-strategygit clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineerWrote 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/rpraharaj/forward-deployed-engineer/context-strategy)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/context-strategy"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/context-strategy.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.1 | $0.00146 | $0.02752 |
| Opus 5 | $0.00073 | $0.01376 |
| Sonnet 5 | $0.00029 | $0.00550 |
| Haiku 4.5 | $0.00015 | $0.00275 |
Grade A, and why
context-strategy 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 6d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context strategy
The craft of staying effective when the system is bigger than what you can hold.
Why this exists
An FDE's only tool is Claude Code, and Claude Code has a finite context window. Enterprise repositories do not respect it — a monorepo with forty thousand files exceeds any window by orders of magnitude, and the naive approach (start reading, keep reading) fails in a specific and expensive way: context fills with low-value file contents, the genuinely important findings get summarized away, and the next session starts from zero and re-derives the same partial map.
The fix isn't reading faster. It's deciding, deliberately and repeatedly, what deserves to occupy context — and writing everything else down where it survives.
When this applies
- A repository too large to survey file by file
- Any engagement spanning more than one session
- Context filling up while a task is unfinished
- Re-discovering something you worked out earlier — the clearest signal this skill is needed
- Before
repo-reconon anything large, to set the budget
When it doesn't
- Small, well-understood repository, single session — just work
- A one-off question with a known answer location
- "Help me understand this repo" when you need a map — that is
repo-recon. Run this first only to set a budget on a large tree.
Prerequisites
Locate the workspace (../_shared/workspace-conventions.md). 00-engagement.md if it exists — it scopes which subtree matters. If there is no workspace yet, still set the budget, write 00c-context.md next to the checkout or after fde-orient creates the workspace, and do not invent a system map.
Procedure
1. Size the problem before entering it
Thirty seconds, and it determines everything downstream. Do not xargs wc the tree or run git log once per file — those hang on the repositories this skill is for.
git ls-files | wc -l
git ls-files | sed 's/.*\.//' | sort | uniq -c | sort -rn | head -15
du -sh .git
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.
- 6d ago First seen · 223 lines · 146 tokens per session scan A 39b3f6df00d0
context-strategy is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 19d ago), licensed MIT. It adds 146 tokens to every session and 2,752 once invoked, about $0.0007 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-31.
Other skills, from other repositories
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.