FlyEnv is a native desktop environment for running local development stacks on Windows, macOS, and Linux, including programming runtimes, databases, web servers, local sites, and developer tools. It is for developers who want to manage these services and project-specific runtime versions from one application.
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/xpf0000/flyenv/flyenv-module-boundariesnpx skills add xpf0000/FlyEnv --skill flyenv-module-boundariesgit clone --depth 1 https://github.com/xpf0000/FlyEnvWrote 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/xpf0000/flyenv/flyenv-module-boundaries)<a href="https://agentmods.dev/skills/xpf0000/flyenv/flyenv-module-boundaries"><img src="https://agentmods.dev/badge/skills/xpf0000/flyenv/flyenv-module-boundaries.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 | $0.00037 | $0.00806 |
| Opus 5 | $0.00018 | $0.00403 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
flyenv-module-boundaries 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 4d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlyEnv Module Boundaries
Treat state ownership as an architecture decision. Assign an owner by lifetime, never by the button or page that first triggers the work.
Default Module Constraints
These are prohibitions unless the user explicitly authorizes an exception for the specific new module:
- Shared configuration: Never persist module-owned state in
config.setup. UseStorageSetAsync/StorageGetAsyncfor module-owned persistence. - Pinia: Do not create a new Pinia store for module-owned state. Use a normal module-local class or singleton and bind it with
reactiveBind. - Lifecycle duplication: Reuse
ModuleInstalledItem.start(),stop(), andrestart()whenever the public lifecycle supports the module. Supply module-specific values throughstartExtParam/stopExtParam, registered in the module (normallycomponents/<Module>/aside.vue). Add a module-specific start/stop workflow only after proving the shared methods cannot express the required behavior. - Public leakage: Keep module-only properties, types, policies, helpers, and methods in the module directory. Do not add them to shared service types,
ModuleInstalledItem,BrewStore, or generic lifecycle helpers.
Record any explicit exception and its scope in the implementation plan. Existing code is not authorization for copying an older pattern.
Required Workflow
- Read
AGENTS.md, including Module Boundaries and Operation Ownership, before editing. - Classify every new state as view, domain, renderer operation, or fork process state.
- Add an operation contract to the plan for every long-running renderer operation.
- Check the Default Module Constraints above and document any explicit exception.
- Implement only after the owner, terminal events, and tests are explicit.
State Owners
| State | Owner |
|---|---|
| Inputs, dialogs, selections, visual filters | Mounted Vue component |
| Existing shared selected versions, installed lists, settings | Pinia or an established module store |
| One asynchronous operation and its UI lifecycle | Module-local singleton controller |
| Child process, PID, port, health, stop ordering | Fork module/runtime |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 51 lines · 37 tokens per session scan A eeb884d0ce7e
flyenv-module-boundaries is a skill published in the GitHub repository xpf0000/FlyEnv (3,190 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 37 tokens to every session and 806 once invoked, about $0.0002 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-30.
Other skills, from other repositories
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
configure-nightwatch
Configures Laravel Nightwatch data collection, sampling rates, filtering rules, and redaction policies. Use when setting up Nightwatch, managing data volume, protecting sensitive data (PII), or optimizing event collection for production workloads.
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
fortify-development
ACTIVATE when the user works on authentication in Laravel. This includes login, registration, password reset, email verification, two-factor authentication (2FA/TOTP/QR codes/recovery codes), passkeys, profile updates, password confirmation, or any auth-related routes and controllers. Activate when the user mentions…
pest-testing
Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to…