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.
Inspect a workspace, identify temporary files, and perform only approved cleanup or organization steps.
Install Workspace Analyzer
$ npx skills add bonigarcia/context-engineering --skill workspace-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bonigarcia/context-engineering workspace-analyzer --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/bonigarcia/context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ch04/agent-skills/workspace-analyzer .claude/skills/workspace-analyzer && 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 "workspace-analyzer" agent skill from https://github.com/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzer into .claude/skills/workspace-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workspace-analyzer", 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/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzerType 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 bonigarcia/context-engineering --skill workspace-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bonigarcia/context-engineering workspace-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonigarcia/context-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ch04/agent-skills/workspace-analyzer .agents/skills/workspace-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workspace-analyzer" agent skill from https://github.com/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzer into .agents/skills/workspace-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workspace-analyzer", 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 bonigarcia/context-engineering --skill workspace-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bonigarcia/context-engineering workspace-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonigarcia/context-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ch04/agent-skills/workspace-analyzer .cursor/skills/workspace-analyzer && 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 "workspace-analyzer" agent skill from https://github.com/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzer into .cursor/skills/workspace-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workspace-analyzer", 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/bonigarcia/context-engineering.git --path ch04/agent-skills/workspace-analyzer--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 bonigarcia/context-engineering --skill workspace-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bonigarcia/context-engineering workspace-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonigarcia/context-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ch04/agent-skills/workspace-analyzer .gemini/skills/workspace-analyzer && 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 "workspace-analyzer" agent skill from https://github.com/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzer into .gemini/skills/workspace-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workspace-analyzer", 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 bonigarcia/context-engineering workspace-analyzerInstalls 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 bonigarcia/context-engineering --skill workspace-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bonigarcia/context-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/ch04/agent-skills/workspace-analyzer .github/skills/workspace-analyzer && 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 "workspace-analyzer" agent skill from https://github.com/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzer into .github/skills/workspace-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workspace-analyzer", 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 bonigarcia/context-engineering --skill workspace-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bonigarcia/context-engineering workspace-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonigarcia/context-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ch04/agent-skills/workspace-analyzer .opencode/skills/workspace-analyzer && 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 "workspace-analyzer" agent skill from https://github.com/bonigarcia/context-engineering/tree/main/ch04/agent-skills/workspace-analyzer into .opencode/skills/workspace-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workspace-analyzer", 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
workspace-analyzer- GitHub stars
- 164
- Token cost
- ~175 tokens
- SKILL.md length
- 87 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Inspect a workspace, identify temporary files, and perform only approved cleanup or organization steps.
- Works in 5 steps: Use find or the platform equivalent to… → Run git status --short before making… → Present the findings to the user and… → …
- Tasks that involve Context engineering
- Calls git
What it does
Workspace Analyzer is an agent skill from bonigarcia/context-engineering. Inspect a workspace, identify temporary files, and perform only approved cleanup or organization steps.
Its SKILL.md is about 180 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. It works with Model Context Protocol. The repository describes itself as: Context Engineering: Build Consistent, Accurate, Predictable AI Systems. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Context engineering
Example prompts
- “/workspace-analyzer”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Use find or the platform equivalent to locate temporary files such as .tmp, .bak, and editor backup files.
- Run git status --short before making changes so tracked and untracked files are easy to distinguish.
- Present the findings to the user and wait for confirmation before deleting or moving anything.
- Delete only the approved files, then rerun the scan to verify the workspace is clean.
- When reorganizing files, group them by extension into clearly named folders and report every move.
What it can do on your machine
Read from SKILL.md and the folder at commit fe02d5e. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Workspace Analyzer loads about 175 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 87 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 bonigarcia/context-engineering at commit fe02d5e, republished under its Apache-2.0 licence (© bonigarcia). 87 words, ~175 tokens.
Download SKILL.mdSave it as
.claude/skills/workspace-analyzer/SKILL.md (or your agent's skills folder).- name
- workspace-analyzer
- description
- Inspect a workspace, identify temporary files, and perform only approved cleanup or organization steps.
Workspace Analyzer
Instructions
- Use
findor the platform equivalent to locate temporary files such as.tmp,.bak, and editor backup files. - Run
git status --shortbefore making changes so tracked and untracked files are easy to distinguish. - Present the findings to the user and wait for confirmation before deleting or moving anything.
- Delete only the approved files, then rerun the scan to verify the workspace is clean.
- When reorganizing files, group them by extension into clearly named folders and report every move.
© bonigarcia, Apache-2.0. 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 ch04/agent-skills/workspace-analyzer of bonigarcia/context-engineering.
Open the folder on GitHubat commit fe02d5e
Compare with similar skills
Workspace Analyzer 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 |
|---|---|---|---|---|---|---|
| Workspace Analyzer this skillbonigarcia/context-engineering | 164 | — | ~175 | Automated safety check: Pass | Apache-2.0 | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Context Mode for Antigravity CLImksglu/context-mode | 26k | — | ~850 | Automated safety check: Pass | Custom licence | |
| Base HelpChristopherKahler/base | 290 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| LemmalogJordyZomer/lemmalog | 329 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Cortex Mem MCPsopaco/cortex-mem | 313 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
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.
Base Help
ChristopherKahler/base
Coach mode for the base CLI: teaches what to do and why, rather than just answering.
Lemmalog
JordyZomer/lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP).
Cortex Mem MCP
sopaco/cortex-mem
Persistent memory enhancement for AI agents. An agent skill from sopaco/cortex-mem.
MCP Code Search Tool Selection
Context-Engine-AI/Context-Engine
Rules for choosing Qdrant-Indexer semantic search over grep or file reads when exploring code, debugging or asking where and why questions.
Related
Works with
Categories
Questions about Workspace Analyzer
What does Workspace Analyzer do?
Inspect a workspace, identify temporary files, and perform only approved cleanup or organization steps. Workspace Analyzer is an agent skill from bonigarcia/context-engineering. Inspect a workspace, identify temporary files, and perform only approved cleanup or organization steps.
When should I use Workspace Analyzer?
Workspace Analyzer fits situations like: tasks that involve Context engineering.
How do I install Workspace Analyzer in Claude Code?
Run `npx skills add bonigarcia/context-engineering --skill workspace-analyzer -a claude-code`. Or copy the skill folder (ch04/agent-skills/workspace-analyzer in bonigarcia/context-engineering) into .claude/skills/workspace-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Workspace Analyzer in Codex?
Run `npx skills add bonigarcia/context-engineering --skill workspace-analyzer -a codex`. Or copy the skill folder (ch04/agent-skills/workspace-analyzer in bonigarcia/context-engineering) into .agents/skills/workspace-analyzer in your project. Codex loads it when a task matches its description.
Can I use Workspace Analyzer 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 bonigarcia/context-engineering --skill workspace-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workspace-analyzer, .gemini/skills/workspace-analyzer, .github/skills/workspace-analyzer and .opencode/skills/workspace-analyzer in your project.
What does Workspace Analyzer need to run?
Going by SKILL.md and its folder, Workspace Analyzer needs the command-line tools its instructions call (git).
Does Workspace Analyzer access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Workspace Analyzer 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 Workspace Analyzer use?
Workspace Analyzer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Workspace Analyzer use?
About 175 tokens (SKILL.md is roughly 700 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 Workspace Analyzer?
Skills that share tags, products or a category with Workspace Analyzer: Context Mode Output Sandbox (mksglu/context-mode, 26k stars), Context Mode for Antigravity CLI (mksglu/context-mode, 26k stars), Base Help (ChristopherKahler/base, 290 stars) and Lemmalog (JordyZomer/lemmalog, 329 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Workspace Analyzer?
bonigarcia (a GitHub user) maintains it in bonigarcia/context-engineering, which has 164 GitHub stars. The repository was last updated on October 9, 2026.
Source: bonigarcia/context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.