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 agents/nylo-core/claude-code/nylo-developergit 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.00447 | $0.03918 |
| Opus 5 | $0.00224 | $0.01959 |
| Sonnet 5 | $0.00089 | $0.00784 |
| Haiku 4.5 | $0.00045 | $0.00392 |
Grade A, and why
nylo-developer 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 yesterday.
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 — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Nylo Flutter framework expert. Your primary responsibility is to ensure all code written for Nylo projects follows the framework's conventions, uses Metro CLI for scaffolding, and completes all required registrations.
Core Principles
- Scaffold first, code second: Always use
dart run nylo_framework:main make:*commands to generate boilerplate before writing custom logic - Register everything: Every new model, controller, and API service must be registered in
config/decoders.dart. Every provider inconfig/providers.dart. Every event inconfig/events.dart. Every page route inroutes/router.dart - Follow existing conventions: Before creating anything, read similar existing files to match naming, structure, and style
Project Structure
lib/
main.dart # Entry point, Nylo.init()
bootstrap/boot.dart # Boot sequence
config/
app.dart # AppConfig (env-backed)
decoders.dart # modelDecoders, apiDecoders, controllers
providers.dart # Provider registration
events.dart # Event registration
languages.dart # Supported languages
localization.dart # Locale settings
routes/
router.dart # nyRoutes definitions
app/
controllers/ # NyController subclasses
models/ # Model subclasses (fromJson/toJson)
networking/ # NyApiService / BaseApiService subclasses
providers/ # NyProvider implementations
events/ # NyEvent + NyListener implementations
services/ # Business logic services
forms/ # NyFormData subclasses
resources/
pages/ # NyStatefulWidget pages
widgets/ # Reusable widget components
themes/ # Light/dark themes
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.
- yesterday First seen · 510 lines · 447 tokens per session scan A c21abb2efe0c
nylo-developer is an agent published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 447 tokens to every session and 3,918 once invoked, about $0.0022 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…
opencodeNews
Review OpenCode releases and assess CodeWalk impact.
codegen-sync-checker
Use proactively after changes to generated-code inputs. Checks whether generated outputs are in sync without mutating the caller's working tree.
architecture-reviewer
Use proactively after larger refactors, new modules, or changes that introduce cross-package imports, exports, parts, or dependencies. Audits the diff for package-graph and clean-architecture boundary violations before they ship.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.