Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Routes file reads, edits, and shell commands through Mirage's own tools instead of host filesystem tools whenever a path is a Mirage-mounted virtual path.
Install Mirage Virtual Filesystem Access
$ npx skills add strukto-ai/mirage --skill mirage-filesystem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install strukto-ai/mirage mirage-filesystem --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/strukto-ai/mirage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/mirage/skills/mirage-filesystem .claude/skills/mirage-filesystem && 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 "mirage-filesystem" agent skill from https://github.com/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystem into .claude/skills/mirage-filesystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirage-filesystem", 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/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystemType 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 strukto-ai/mirage --skill mirage-filesystem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install strukto-ai/mirage mirage-filesystem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/strukto-ai/mirage.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/mirage/skills/mirage-filesystem .agents/skills/mirage-filesystem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mirage-filesystem" agent skill from https://github.com/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystem into .agents/skills/mirage-filesystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirage-filesystem", 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 strukto-ai/mirage --skill mirage-filesystem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install strukto-ai/mirage mirage-filesystem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/strukto-ai/mirage.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/mirage/skills/mirage-filesystem .cursor/skills/mirage-filesystem && 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 "mirage-filesystem" agent skill from https://github.com/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystem into .cursor/skills/mirage-filesystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirage-filesystem", 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/strukto-ai/mirage.git --path plugins/mirage/skills/mirage-filesystem--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 strukto-ai/mirage --skill mirage-filesystem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install strukto-ai/mirage mirage-filesystem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/strukto-ai/mirage.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/mirage/skills/mirage-filesystem .gemini/skills/mirage-filesystem && 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 "mirage-filesystem" agent skill from https://github.com/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystem into .gemini/skills/mirage-filesystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirage-filesystem", 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 strukto-ai/mirage mirage-filesystemInstalls 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 strukto-ai/mirage --skill mirage-filesystem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/strukto-ai/mirage.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/mirage/skills/mirage-filesystem .github/skills/mirage-filesystem && 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 "mirage-filesystem" agent skill from https://github.com/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystem into .github/skills/mirage-filesystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirage-filesystem", 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 strukto-ai/mirage --skill mirage-filesystem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install strukto-ai/mirage mirage-filesystem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/strukto-ai/mirage.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/mirage/skills/mirage-filesystem .opencode/skills/mirage-filesystem && 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 "mirage-filesystem" agent skill from https://github.com/strukto-ai/mirage/tree/main/plugins/mirage/skills/mirage-filesystem into .opencode/skills/mirage-filesystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mirage-filesystem", 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
mirage-filesystem- GitHub stars
- 3.7k
- Token cost
- ~264 tokens
- SKILL.md length
- 130 words
- Files
- 2
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Routes file reads, edits, and shell commands through Mirage's own tools instead of host filesystem tools whenever a path is a Mirage-mounted virtual path.
- Works in 5 steps: Use the Mirage ls, glob, grep, or shell… → Use the Mirage read tool before… → Use edit for an existing file and write… → …
- Inspecting or editing a file exposed through a Mirage virtual path
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Searching mounted cloud or database data with Mirage tools
What it does
This skill covers discovering mounted cloud or database data with Mirage's own ls, glob, grep, or shell tools, since host filesystem tools can't see those virtual paths unless the user separately set up a FUSE mount, and always reads an existing file with Mirage's read tool before editing it.
It uses edit only for files that already exist and write only for new ones, and when an edit is rejected because the file changed since it was read, it re-reads the file, reconsiders the edit against the new content, and retries rather than forcing the old edit through. It never falls back to a host tool when a Mirage tool fails on a virtual path, reporting the Mirage error or fixing the Mirage configuration instead.
When your agent uses it
- Inspecting or editing a file exposed through a Mirage virtual path
- Searching mounted cloud or database data with Mirage tools
- Recovering from a stale-read edit conflict on a Mirage path
Example prompts
- “List the files mounted under this Mirage virtual path.”
- “Edit this file exposed through Mirage without touching the host filesystem.”
- “Search the mounted database data for this keyword.”
Requirements
- A configured Mirage virtual filesystem mount
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Use the Mirage ls, glob, grep, or shell tool to discover mounted data.
- Use the Mirage read tool before modifying an existing file.
- Use edit for an existing file and write only for a new file.
- If an edit reports that the file changed since it was read, read the file again, reconsider the edit against the new content, and retry.
- Use shell for pipelines and structured-file commands that need Mirage shell semantics.
What it can do on your machine
Read from SKILL.md and the folder at commit 9e61942. 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
Mirage Virtual Filesystem Access loads about 264 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 130 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 strukto-ai/mirage at commit 9e61942, republished under its Apache-2.0 licence (© strukto-ai). 130 words, ~264 tokens.
Download SKILL.mdSave it as
.claude/skills/mirage-filesystem/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- mirage-filesystem
- description
- Work with files and directories mounted in a Mirage virtual filesystem. Use when a task mentions Mirage, mounted cloud or database data, Mirage virtual paths, or asks to inspect, search, create, or edit data exposed through the Mirage tools.
Mirage Filesystem
Use the Mirage tools for virtual paths. Host filesystem tools cannot access those paths unless the user separately configured a FUSE mount.
Workflow
- Use the Mirage
ls,glob,grep, orshelltool to discover mounted data. - Use the Mirage
readtool before modifying an existing file. - Use
editfor an existing file andwriteonly for a new file. - If an edit reports that the file changed since it was read, read the file again, reconsider the edit against the new content, and retry.
- Use
shellfor pipelines and structured-file commands that need Mirage shell semantics.
Do not fall back to a host filesystem tool when a Mirage tool fails on a virtual path. Report the Mirage error or fix the Mirage configuration.
© strukto-ai, 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
SKILL.md and 1 other file in plugins/mirage/skills/mirage-filesystem of strukto-ai/mirage.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 9e61942
Compare with similar skills
Mirage Virtual Filesystem Access 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 |
|---|---|---|---|---|---|---|
| Mirage Virtual Filesystem Access this skillstrukto-ai/mirage | 3.7k | — | ~264 | Automated safety check: Pass | Apache-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from strukto-ai/mirage
Mirage VFS Adapter Authoring
strukto-ai/mirage
Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.
Related
Categories
Questions about Mirage Virtual Filesystem Access
What does Mirage Virtual Filesystem Access do?
Routes file reads, edits, and shell commands through Mirage's own tools instead of host filesystem tools whenever a path is a Mirage-mounted virtual path. This skill covers discovering mounted cloud or database data with Mirage's own ls, glob, grep, or shell tools, since host filesystem tools can't see those virtual paths unless the user separately set up a FUSE mount, and always reads an existing file with Mirage's read tool before editing it.
When should I use Mirage Virtual Filesystem Access?
Mirage Virtual Filesystem Access fits situations like: inspecting or editing a file exposed through a Mirage virtual path; searching mounted cloud or database data with Mirage tools; recovering from a stale-read edit conflict on a Mirage path.
How do I install Mirage Virtual Filesystem Access in Claude Code?
Run `npx skills add strukto-ai/mirage --skill mirage-filesystem -a claude-code`. Or copy the skill folder (plugins/mirage/skills/mirage-filesystem in strukto-ai/mirage) into .claude/skills/mirage-filesystem in your project. Claude Code loads it when a task matches its description.
How do I install Mirage Virtual Filesystem Access in Codex?
Run `npx skills add strukto-ai/mirage --skill mirage-filesystem -a codex`. Or copy the skill folder (plugins/mirage/skills/mirage-filesystem in strukto-ai/mirage) into .agents/skills/mirage-filesystem in your project. Codex loads it when a task matches its description.
Can I use Mirage Virtual Filesystem Access 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 strukto-ai/mirage --skill mirage-filesystem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mirage-filesystem, .gemini/skills/mirage-filesystem, .github/skills/mirage-filesystem and .opencode/skills/mirage-filesystem in your project.
What does Mirage Virtual Filesystem Access need to run?
SKILL.md names no scripts, command-line tools or credentials: Mirage Virtual Filesystem Access is instructions for the agent only. Our summary lists: A configured Mirage virtual filesystem mount.
Does Mirage Virtual Filesystem Access 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 Mirage Virtual Filesystem Access 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 Mirage Virtual Filesystem Access use?
Mirage Virtual Filesystem Access 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 Mirage Virtual Filesystem Access use?
About 264 tokens (SKILL.md is roughly 1.1k 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 Mirage Virtual Filesystem Access?
Skills that share tags, products or a category with Mirage Virtual Filesystem Access: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mirage Virtual Filesystem Access?
strukto-ai (a GitHub organization) maintains it in strukto-ai/mirage, which has 3,682 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 11, 2026.
Source: strukto-ai/mirage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.