filesystem-context

Offload agent context to filesystem files for scratchpads, plans, and sub-agent workspaces.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill filesystem-context-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: filesystem-context
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/filesystem-context
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill filesystem-context-sambhav242005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? LLM context windows are limited, and large tool outputs, long-running plans, and multi-agent coordination quickly exhaust available tokens. This Skill provides patterns and utilities for using the filesystem as a persistent overflow layer so agents store, retrieve, and update context on demand instead of keeping everything in the prompt. ## Core Features & Use Cases - Tool Output Offloading: Automatically write large tool outputs (over ~2000 tokens) to scratch files and return compact references with summaries. - Plan Persistence: Save structured multi-step plans to disk so agents can re-read objectives and progress after context refreshes or summarization. - Sub-Agent Workspaces: Route sub-agent findings through per-agent directories instead of lossy message chains, with dynamic skill loading and terminal output persistence. - Use Case: A research agent runs a web search returning 8000 tokens. The Skill writes results to a scratch file, returns a 100-token reference, and the agent greps the file later for specific details. ## Quick Start Ask the agent to offload any tool output larger than 2000 tokens to a scratch file and return only a summary with the file path.

Frequently Asked Questions about filesystem-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce LLM context window usage for large tool outputs?

Write outputs exceeding roughly 2000 tokens to a scratch file and return a compact reference with a summary instead. The agent can later grep the file or read specific line ranges to retrieve only what it needs.

How to persist agent plans across context window refreshes?

Serialize the plan as structured JSON or YAML with step IDs, descriptions, and statuses, then save it to disk. The agent re-reads the file at the start of each turn or after summarization to restore task awareness.

When should I use filesystem context instead of keeping everything in the prompt?

Use it when tool outputs exceed about 2000 tokens, tasks span multiple turns, or multiple agents share state. Avoid it for single-turn tasks, when context fits comfortably, or when file I/O latency is critical.

Can multiple agents share information through files instead of messages?

Yes, each sub-agent writes findings to its own isolated workspace directory, and the coordinator reads those files directly. This avoids the summarization degradation that occurs in multi-hop message chains.

What are the risks of agent self-modification of preference files?

Self-modification can accumulate incorrect or contradictory instructions over time. Guard it with validation such as entry limits, value length caps, and periodic human review of persisted preferences.