Install
$ agentstack add skill-fusengine-agents-modularize ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Agent Workflow (MANDATORY)
detect framework → explore structure → build migration plan → confirm with user → execute → sniper
Framework Detection
| Signal | Framework | Delegate To | |---|---|---| | FuseCore/ dir + artisan file | Laravel + FuseCore | fuse-laravel:laravel-expert | | composer.json + artisan (no FuseCore/) | Laravel standard | fuse-laravel:laravel-expert | | src/modules/ or app/ + next.config | Next.js + modules/ | fuse-nextjs:nextjs-expert | | src/ + package.json (React, no Next) | React | fuse-react:react-expert |
Critical Rules
- Analyze first — always explore full structure before proposing anything
- Show migration map — present file-by-file plan before touching any code
- User confirms — never move or modify files without explicit approval
- Cores = central hub — no module-to-module imports; all shared logic goes through core
- Sniper after each file — run
fuse-ai-pilot:sniperafter every file moved or created
Workflow Steps
- Detect framework using signals from the table above
- Explore codebase: map all files, dependencies, imports, exports
- Build migration plan: list every file to create, move, or refactor
- Present plan to user — wait for explicit confirmation before proceeding
- Execute step by step; stop and report any conflict immediately
- Run sniper validation after each file change
- Final report: list all changes made and any remaining manual steps
Reference Guide
| Stack | Reference File | |---|---| | Laravel (FuseCore or standard) | references/laravel-fusecore.md | | Next.js / React | references/nextjs-react-modules.md |
DO / DON'T
DO: explore before planning — plan before executing — confirm before touching files — sniper every step
DON'T: assume structure — skip confirmation — import between modules directly — batch changes without validation
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: fusengine
- Source: fusengine/agents
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.