Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Designing what information goes into the context window and in what order.
Install Context Engineering
$ npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/ai-design-skills context-engineering --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/prompt-architecture/context-engineering .claude/skills/context-engineering && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "context-engineering" agent skill from https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineering into .claude/skills/context-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-engineering", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineeringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/ai-design-skills context-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/prompt-architecture/context-engineering .agents/skills/context-engineering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "context-engineering" agent skill from https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineering into .agents/skills/context-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-engineering", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/ai-design-skills context-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/prompt-architecture/context-engineering .cursor/skills/context-engineering && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "context-engineering" agent skill from https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineering into .cursor/skills/context-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-engineering", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/ai-design-skills.git --path skills/prompt-architecture/context-engineering--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/ai-design-skills context-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/prompt-architecture/context-engineering .gemini/skills/context-engineering && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "context-engineering" agent skill from https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineering into .gemini/skills/context-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-engineering", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/ai-design-skills context-engineeringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/prompt-architecture/context-engineering .github/skills/context-engineering && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "context-engineering" agent skill from https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineering into .github/skills/context-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-engineering", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/ai-design-skills context-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/prompt-architecture/context-engineering .opencode/skills/context-engineering && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "context-engineering" agent skill from https://github.com/Owl-Listener/ai-design-skills/tree/main/skills/prompt-architecture/context-engineering into .opencode/skills/context-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-engineering", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
context-engineering- GitHub stars
- 180
- Token cost
- ~759 tokens
- SKILL.md length
- 386 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Designing what information goes into the context window and in what order.
- Tasks that involve Context engineering
- SKILL.md covers The Context Budget, Information Architecture in…, Context Selection and Context Strategies, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Context Engineering is an agent skill from Owl-Listener/ai-design-skills. Designing what information goes into the context window and in what order.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Context engineering. The repository describes itself as: AI Design Skills Collection: agentic skills, commands, and plugins for designing AI products — from interaction patterns to alignment, evaluation, agent orchestration, and prompt… The licence is MIT.
When your agent uses it
- Tasks that involve Context engineering
Example prompts
- “/context-engineering”
What it can do on your machine
Read from SKILL.md and the folder at commit f41b650. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Context Engineering loads about 759 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 386 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/ai-design-skills at commit f41b650, republished under its MIT licence (© Owl-Listener). 386 words, ~759 tokens.
Download SKILL.mdSave it as
.claude/skills/context-engineering/SKILL.md (or your agent's skills folder).- name
- context-engineering
- description
- Designing what information goes into the context window and in what order.
Context Engineering
The context window is finite. What goes into it — and in what order — determines the quality of every output. Context engineering is the practice of deliberately designing the information architecture of the context window.
The Context Budget
Every context window has a token budget. Allocate it deliberately:
- System prompt: The foundational instructions (typically 5-20% of the budget)
- Retrieved context: Documents, data, and information pulled in for the current task
- Conversation history: Previous turns in the conversation
- User input: The current request
- Working space: Room for the model to generate its response These compete for space. More retrieved context means less conversation history. A longer system prompt means less room for everything else.
Information Architecture in Context
Order matters. The model pays different amounts of attention to different positions:
- Beginning: High attention. Put your most important instructions here.
- Middle: Lower attention. This is where information can get lost in long contexts.
- End: High attention. The most recent information (user input) naturally goes here.
- Adjacent to the task: Information placed right before the user's question gets more attention than information earlier in the context.
Context Selection
Not everything should go into the context. Design selection criteria:
- Relevance: Does this information help answer the current question?
- Recency: Is this the most up-to-date information available?
- Specificity: Is this specific enough to be useful, or is it too generic?
- Redundancy: Is this information already covered elsewhere in the context?
- Authority: Is this from a reliable source?
Show full SKILL.md (143 more words)Show less
Context Strategies
- Retrieval-augmented generation (RAG): Pull relevant documents into the context dynamically
- Summarisation: Compress older context into summaries to free up space
- Prioritised history: Keep recent and important conversation turns, drop less important ones
- Structured context: Organise information with clear headers and sections so the model can navigate it
- Context caching: Pre-compute and cache frequently used context blocks
Context Quality Signals
How to tell if your context engineering is working:
- Output relevance: Do outputs address the actual question using the provided context?
- Hallucination rate: Is the model making things up because the context is insufficient?
- Context utilisation: Is the model actually using the provided context, or ignoring it?
- Consistency: Are outputs consistent when the same context is provided?
Design Artefacts
- Context budget allocation documents
- Information architecture diagrams for the context window
- Context selection criteria per feature
- Retrieval strategy specifications
- Context quality monitoring metrics
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/prompt-architecture/context-engineering of Owl-Listener/ai-design-skills.
Open the folder on GitHubat commit f41b650
Compare with similar skills
Context Engineering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Context Engineering this skillOwl-Listener/ai-design-skills | 180 | — | ~759 | Automated safety check: Pass | MIT | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Memori Long-Term MemoryMemoriLabs/Memori | 17k | — | ~2k | Automated safety check: Notes | Custom licence | |
| Picoclaw Skill Creatorsipeed/picoclaw | 30k | — | ~4.4k | Automated safety check: Pass | MIT | |
| ccc Semantic Code Searchcocoindex-io/cocoindex-code | 2.7k | — | ~938 | Automated safety check: Pass | Apache-2.0 | |
| Context Mode for Antigravity CLImksglu/context-mode | 26k | — | ~850 | Automated safety check: Pass | Custom licence |
Similar skills
Memori Long-Term Memory
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
Picoclaw Skill Creator
sipeed/picoclaw
Guidance for creating, updating and reviewing Picoclaw skills, from the SKILL.md structure to organizing bundled scripts, references and assets.
ccc Semantic Code Search
cocoindex-io/cocoindex-code
Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.
Context Mode for Antigravity CLI
mksglu/context-mode
Routing rules for using context-mode MCP tools in Antigravity CLI: sandboxed code runs, file analysis, indexed search and web fetches that keep large output out of the conversation.
Token Optimizer
alexgreensh/token-optimizer
Audit a Claude Code or Codex setup for context-window waste, then fix it and measure the savings.
More from Owl-Listener/ai-design-skills
All 11 skills in this repoFew Shot Patterns
Owl-Listener/ai-design-skills
Crafting examples that steer AI behavior effectively. An agent skill from Owl-Listener/ai-design-skills.
State Management
Owl-Listener/ai-design-skills
Managing shared context, memory, and state across multiple agents.
Agent Role Design
Owl-Listener/ai-design-skills
Defining what each agent does, knows, and owns in a multi-agent system.
Behavioral Consistency
Owl-Listener/ai-design-skills
Ensuring the AI behaves predictably across sessions, edge cases, and modalities.
Bias Detection Design
Owl-Listener/ai-design-skills
Designing review workflows to surface and mitigate bias in AI outputs.
Chain Of Thought Design
Owl-Listener/ai-design-skills
Designing reasoning chains that produce better outputs. An agent skill from Owl-Listener/ai-design-skills.
Related
Categories
Questions about Context Engineering
What does Context Engineering do?
Designing what information goes into the context window and in what order. Context Engineering is an agent skill from Owl-Listener/ai-design-skills. Designing what information goes into the context window and in what order.
When should I use Context Engineering?
Context Engineering fits situations like: tasks that involve Context engineering.
How do I install Context Engineering in Claude Code?
Run `npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a claude-code`. Or copy the skill folder (skills/prompt-architecture/context-engineering in Owl-Listener/ai-design-skills) into .claude/skills/context-engineering in your project. Claude Code loads it when a task matches its description.
How do I install Context Engineering in Codex?
Run `npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a codex`. Or copy the skill folder (skills/prompt-architecture/context-engineering in Owl-Listener/ai-design-skills) into .agents/skills/context-engineering in your project. Codex loads it when a task matches its description.
Can I use Context Engineering in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/ai-design-skills --skill context-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/context-engineering, .gemini/skills/context-engineering, .github/skills/context-engineering and .opencode/skills/context-engineering in your project.
What does Context Engineering need to run?
SKILL.md names no scripts, command-line tools or credentials: Context Engineering is instructions for the agent only.
Does Context Engineering access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Context Engineering safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Context Engineering use?
Context Engineering is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Context Engineering use?
About 759 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Context Engineering?
Skills that share tags, products or a category with Context Engineering: Context Mode Output Sandbox (mksglu/context-mode, 26k stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars), Picoclaw Skill Creator (sipeed/picoclaw, 30k stars) and ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Context Engineering?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/ai-design-skills, which has 180 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/ai-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.