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 skills add nylo-core/claude-code --skill nylo-v6-to-v7-migrationgit 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/skills/nylo-core/claude-code/nylo-v6-to-v7-migration)<a href="https://agentmods.dev/skills/nylo-core/claude-code/nylo-v6-to-v7-migration"><img src="https://agentmods.dev/badge/skills/nylo-core/claude-code/nylo-v6-to-v7-migration.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.00036 | $0.02580 |
| Opus 5 | $0.00018 | $0.01290 |
| Sonnet 5 | $0.00007 | $0.00516 |
| Haiku 4.5 | $0.00004 | $0.00258 |
Grade A, and why
nylo-v6-to-v7-migration 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 8d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nylo v6 to v7 Migration
Spawn the nylo-v6-to-v7-migrator agent to migrate the current Nylo Flutter project from v6 to v7. The agent handles the full migration — discovery, task list, implementation, and verification.
When to Use
- User wants to migrate a Nylo Flutter v6 project to v7
- User is getting errors after updating Nylo dependencies to v7
- User asks about v6-to-v7 breaking changes
Steps
-
Spawn the migrator agent using the
nylo-v6-to-v7-migratoragent type. The agent will:- Scan the v7 boilerplate and changelog
- Analyze the user's v6 project
- Present a migration task list for approval
- Implement changes one category at a time
-
After the agent completes, run a post-migration verification pass using the maps below.
Complete v6 → v7 Structure Map
Root Level Changes
| v6 | v7 | Action |
|---|---|---|
public/ |
assets/ |
Renamed |
public/app_icon/icon.png |
assets/app_icon/icon.png |
Moved with parent |
public/fonts/ |
assets/fonts/ |
Moved with parent |
public/images/logo.png |
assets/images/logo.png |
Moved with parent |
public/postman/ |
(removed) | Deleted entirely |
.env |
(generated, gitignored) | Removed from repo — generated via make:env |
lang/en.json |
lang/en.json |
Stays, but must add required nylo translation keys |
| — | lang/es.json |
New in v7 (optional extra locale) |
lib/app/commands/
| v6 | v7 | Action |
|---|---|---|
custom_commands.json |
commands.json |
Renamed |
current_time.dart |
current_time.dart |
No change |
motivational_quote.dart |
motivational_quote.dart |
No change |
| — | download_fonts.dart |
New in v7 |
lib/app/events/
| v6 | v7 | Action |
|---|---|---|
logout_event.dart |
logout_event.dart |
No change |
| — | authenticated_event.dart |
New in v7 (for post-auth navigation) |
lib/app/forms/
| v6 | v7 | Action |
|---|---|---|
login_form.dart |
(removed) | Removed from boilerplate |
register_form.dart |
register_form.dart |
Stays, but NyFormData → NyFormWidget, validate: → validator: |
style/form_style.dart |
(removed) | Entire style/ subdirectory removed |
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.
- 8d ago First seen · 218 lines · 36 tokens per session scan A f22161995bad
nylo-v6-to-v7-migration is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 2,580 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-31.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-database
Use when syncing real-time data, structuring JSON trees, reading/writing, creating listeners, enabling offline persistence, managing presence, sharding, or writing security rules.
flutter-app-architecture
Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).