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-state-managementnpx skills add nylo-core/claude-code --skill nylo-state-managementgit 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-state-management)<a href="https://agentmods.dev/skills/nylo-core/claude-code/nylo-state-management"><img src="https://agentmods.dev/badge/skills/nylo-core/claude-code/nylo-state-management.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 | $0.00056 | $0.03077 |
| Opus 5 | $0.00028 | $0.01538 |
| Sonnet 5 | $0.00011 | $0.00615 |
| Haiku 4.5 | $0.00006 | $0.00308 |
Grade A, and why
nylo-state-management 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 3d 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 — 568 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nylo State Management
Overview
Nylo v7 state management is built on two core classes: NyState (for reusable widgets) and NyPage (for pages, extending NyState). State updates propagate through named state identifiers, state actions enable cross-widget communication, and the provider/event systems handle app-level initialization and event-driven logic. Decoders bridge API responses to typed models.
When to Use
- Building stateful widgets that need to update from external triggers
- Managing page lifecycle (init, loading, reboot)
- Communicating between widgets via state actions
- Locking UI during async operations (e.g. preventing double-submit)
- Registering app services and packages via providers
- Dispatching and listening to application events
- Registering model decoders for API response parsing
- When NOT to use: for simple local state within a single widget, standard Flutter
setStateis sufficient
Quick Reference
| Task | Code |
|---|---|
| Create stateful widget | metro make:stateful_widget my_widget |
| Create state-managed widget | metro make:state_managed_widget cart |
| Update a widget's state | updateState(Cart.state) |
| Update with data | updateState(Cart.state, data: "value") |
| Fire a state action | stateAction('refresh', state: MyWidget.state) |
| Lock during async | lockRelease('key', perform: () async { ... }) |
| Check if locked | isLocked('key') |
| Check if loading | isLoading(name: 'key') |
| Reboot page init | reboot() |
| Create provider | metro make:provider cache_provider |
| Create event | metro make:event payment_event |
| Dispatch event | event<PaymentEvent>(data: {...}) |
NyState
Basic Structure
class MyWidget extends StatefulWidget {
static String state = "my_widget";
@override
_MyWidgetState createState() => _MyWidgetState();
}
class _MyWidgetState extends NyState<MyWidget> {
_MyWidgetState() {
stateName = MyWidget.state;
}
@override
get init => () async {
// Async initialization - loader shown automatically
};
@override
void stateUpdated(data) {
// Called when updateState(MyWidget.state) is invoked
reboot(); // Re-run init to refresh data
}
@override
Widget view(BuildContext context) {
return Scaffold(
body: Text("My Widget"),
);
}
}
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.
- 3d ago First seen · 568 lines · 56 tokens per session scan A b708eb95b40f
nylo-state-management is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 3,077 once invoked, about $0.0003 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.