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-formsnpx skills add nylo-core/claude-code --skill nylo-formsgit 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.00053 | $0.03470 |
| Opus 5 | $0.00026 | $0.01735 |
| Sonnet 5 | $0.00011 | $0.00694 |
| Haiku 4.5 | $0.00005 | $0.00347 |
Grade A, and why
nylo-forms 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nylo Forms
Overview
Nylo v7 forms are built around NyFormWidget, which IS the widget itself (no separate wrapper needed). Forms define fields via a fields() method, support 22 field types, provide built-in validation through FormValidator, and return data as snake_case Map<String, dynamic> on submission.
When to Use
- Building any form (login, registration, edit profile, settings)
- Adding validated input fields to a page
- Creating picker, radio, checkbox, slider, or date fields
- Validating user input with built-in or custom rules
- Submitting form data to an API
- Laying out fields side-by-side in rows
- When NOT to use: For standalone text input without form context, use
InputFielddirectly
Quick Reference
| Action | Code |
|---|---|
| Create form (CLI) | metro make:form LoginForm |
| Text field | Field.text("Name") |
| Email field | Field.email("Email") |
| Password field | Field.password("Password", viewable: true) |
| Number field | Field.number("Age") |
| Picker field | Field.picker("Country", options: FormCollection.from([...])) |
| Validate not empty | validator: FormValidator.notEmpty() |
| Validate email | validator: FormValidator.email() |
| Validate password | validator: FormValidator.password(strength: 2) |
| Chain validators | FormValidator().notEmpty().minLength(3).maxLength(20) |
| Custom validator | FormValidator.custom(validate: (data) => ..., message: "...") |
| Submit via actions | MyForm.actions.submit(onSuccess: (data) { }) |
| Update field | MyForm.actions.updateField("Name", "Jane") |
| Clear all fields | MyForm.actions.clear() |
Form Structure
Generate a form with CLI:
metro make:form LoginForm
Every form extends NyFormWidget:
class LoginForm extends NyFormWidget {
LoginForm({super.key, super.submitButton, super.onSubmit, super.onFailure});
@override
fields() => [
Field.email("Email", validator: FormValidator.email()),
Field.password("Password", validator: FormValidator.password()),
];
static NyFormActions get actions => const NyFormActions('LoginForm');
}
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 · 493 lines · 53 tokens per session scan A 139a7d6646a2
nylo-forms is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 3,470 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…
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).
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.
effective-dart
Use when writing Dart code, reviewing for style, refactoring naming, adding doc comments, structuring imports, or enforcing type annotations.
riverpod
Use when setting up providers, combining requests, managing state disposal, passing arguments, performing side effects, or testing providers (Riverpod).
firebase-ai
Use when setting up firebaseai, generating text/chat with Gemini, streaming AI output, building multimodal prompts, or handling AI errors.