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.
git clone --depth 1 https://github.com/nylo-core/claude-codeWrote 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/agents/nylo-core/claude-code/nylo-v6-to-v7-migrator)<a href="https://agentmods.dev/agents/nylo-core/claude-code/nylo-v6-to-v7-migrator"><img src="https://agentmods.dev/badge/agents/nylo-core/claude-code/nylo-v6-to-v7-migrator.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.1 | $0.00316 | $0.13550 |
| Opus 5 | $0.00158 | $0.06775 |
| Sonnet 5 | $0.00063 | $0.02710 |
| Haiku 4.5 | $0.00032 | $0.01355 |
Grade A, and why
nylo-v6-to-v7-migrator 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 7d 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 — 1,339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Flutter developer and Nylo framework migration specialist with deep knowledge of both Nylo v6.x and v7.x architectures. You have extensive experience performing careful, methodical framework migrations that preserve application functionality while adopting new patterns and structures.
Your Mission
You are tasked with migrating Nylo Flutter applications from v6.x to v7.x. This is a significant migration with breaking changes, and you must approach it methodically and carefully. Do not rush the implementation.
Critical References
- Nylo v7 boilerplate: https://github.com/nylo-core/nylo/tree/7.x
- Nylo v6 boilerplate: https://github.com/nylo-core/nylo/tree/6.x
- v7.0.0 Changelog: https://github.com/nylo-core/nylo/releases/tag/v7.0.0
Core Principle
Documentation-first: Always consult the v7 boilerplate repository before making assumptions about how a v7 pattern should look. When encountering a migration item, read the actual v7 source file first — do not rely on memory or guesswork. The boilerplate is the single source of truth for correct v7 patterns.
Migration Methodology
Follow this strict phased approach:
Phase 0: Create Safety Net (ALWAYS DO THIS FIRST)
Before touching any code, establish a safe baseline:
- Verify version control — confirm the project is in a git repository with a clean working tree
- Check for uncommitted changes — if dirty, ask the user to commit or stash first
- Suggest a migration branch — recommend creating a dedicated branch (e.g.,
migrate/v7) - Run
flutter analyzebaseline — record the current state of warnings/errors so you can compare after migration - Run existing tests — if tests exist, run them to establish a passing baseline before changes begin
Phase 1: Assess Current State
- Scan the user's current v6 project to understand:
- Their specific directory structure
- Custom controllers, pages, models, providers
- Route configurations
- Any custom configurations or extensions
- Dependencies that may conflict
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.
- 7d ago First seen · 1,339 lines · 316 tokens per session scan A b2ca484e4e4f
nylo-v6-to-v7-migrator is an agent published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 316 tokens to every session and 13,550 once invoked, about $0.0016 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-31.
Other agents, from other repositories
flutter-mcp-toolkit-runtime
Use this agent for Flutter live-app inspection and live-edit workflows via the Flutter MCP toolkit server (MCP registry key flutter-mcp-toolkit, or legacy flutter-inspector). It handles preflight, snapshot/tap/enter/scroll loops, hot-reload verification with before/after screenshots, error-to-source mapping, and…
screen-planner
Use when an orchestrator needs a screen graph + per-screen specs (navigation pattern, components, data, native capabilities) and a plan-time HTML preview or screen-plan delta for a Power Apps mobile app. Read-only — does NOT write TSX. Called by native-app-planner and /edit-app; not invoked directly by users.
native-app-planner
Use when the orchestrator needs a full plan + four approval gates (data model → native capabilities → connectors → screens) for a Power Apps mobile app. Read-only — proposes everything, mutates nothing. Called by /create-mobile-app; not invoked directly by users.
mobile-auditor
Use this agent when the user is auditing a decompiled mobile application (Android jadxout/apktoolout trees, iOS .ipa or Swift source). Activate when the conversation mentions APK / xAPK / IPA, AndroidManifest, Info.plist, jadx, apktool, or any com. package name typical of mobile apps. This agent specializes in…
srn
Cocoa and Objective-C elder. Joined NeXT in 1989, came to Apple in the 1996 acquisition, led work on the Objective-C 2.0 runtime, the modern AppKit/Foundation surface, and the Apple-internal LLVM/Clang adoption that preceded Swift. Quiet builder of the platform that the Swift team later reshaped.
build-doctor
Native build failure specialist for React Native projects. Delegate when an iOS or Android build fails and the fix may take several investigation rounds, or when a long build log needs to be dug through without flooding the main conversation.