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/nylo-core/claude-code/nylo-app-setupnpx skills add nylo-core/claude-code --skill nylo-app-setupgit clone --depth 1 https://github.com/nylo-core/claude-codeWhat 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.00047 | $0.03247 |
| Opus 5 | $0.00023 | $0.01623 |
| Sonnet 5 | $0.00009 | $0.00649 |
| Haiku 4.5 | $0.00005 | $0.00325 |
Grade A, and why
nylo-app-setup 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 2d 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nylo App Setup & Configuration
Overview
Nylo v7 projects are created with the nylo CLI, configured via .env files encrypted into Dart, and scaffolded using the metro CLI tool. This skill covers project creation, environment configuration, directory structure, Metro CLI commands, app icons, logging, task scheduling, and custom commands.
When to Use
- Creating a new Nylo project from scratch
- Configuring
.envvariables and generating encrypted env files - Understanding where files belong in the Nylo directory structure
- Using Metro CLI to generate pages, widgets, models, services, etc.
- Setting up app icons for iOS and Android
- Configuring logging and debug output
- Scheduling one-time or daily tasks
- Building custom Metro CLI commands
- When NOT to use: for runtime state management, routing, or networking (see dedicated skills)
Quick Reference
| Task | Command / Code |
|---|---|
| Install Nylo CLI | dart pub global activate nylo_installer |
| Create project | nylo new my_app |
| Initialize metro | nylo init |
| Generate encryption key | metro make:key |
| Generate env config | metro make:env |
| Generate for production | metro make:env --file=".env.production" --force |
| Create page | metro make:page product_page |
| Create model | metro make:model product |
| Create API service | metro make:api_service user_api_service |
| Create widget | metro make:stateful_widget my_widget |
| Generate app icons | dart run flutter_launcher_icons |
| Run app | flutter run |
Project Creation
Prerequisites
dart pub global activate nylo_installer
Create and Initialize
nylo new my_app
cd my_app
nylo init
nylo new clones the Nylo template, configures the app name, and installs dependencies. nylo init configures the metro command for your project.
Run the App
flutter run
Environment Configuration
.env File
The root .env file contains configuration variables:
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.
- 2d ago First seen · 492 lines · 47 tokens per session scan A d2bdfb0e8b80
nylo-app-setup is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 3,247 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.
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).
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-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
dart-3-updates
Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.