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 noerd-dev/noerd --skill noerd-modal-developmentgit clone --depth 1 https://github.com/noerd-dev/noerdWrote 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/noerd-dev/noerd/noerd-modal-development)<a href="https://agentmods.dev/skills/noerd-dev/noerd/noerd-modal-development"><img src="https://agentmods.dev/badge/skills/noerd-dev/noerd/noerd-modal-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/noerd-dev/noerd/noerd-modal-development"><img src="https://agentmods.dev/badge/skills/noerd-dev/noerd/noerd-modal-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00153 | $0.01601 |
| Opus 5.5 | $0.00061 | $0.00640 |
| Sonnet 5.5 | $0.00031 | $0.00320 |
| Haiku 4.5 | $0.00015 | $0.00160 |
Grade A, and why
noerd-modal-development 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 1mo 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Noerd Modal Development
Every backend modal uses the noerd modal system — never a hand-rolled fixed inset-0 overlay or an
Alpine x-show dialog inside a component. A dropdown menu is not a modal: it uses
<x-noerd::action-menu> (see docs/action-menu.md), and is equally never hand-rolled. Hard rules: noerd/noerd Boost guideline (Core Rules,
"Route modal vs. component modal"). Full reference: vendor/noerd/noerd/docs/modal.md.
1. Route or component? (decide first)
Ask: paste the resulting URL into a fresh tab — does it show the same thing?
| Yes → route modal | No → component modal |
|---|---|
ONE addressable record (*-detail, *-page, or a list that IS a record, e.g. the per-record settings list of an object) |
action dialogs (*-modal, *-confirmation, *-review, *-import, *-editor) |
Noerd::modalRoute('{app}.{entity}.detail', ['modelId' => $id]) / $modalRoute(...) |
Noerd::modal('{module}::{component}', ['key' => $value]) / $modal(...) |
URL rewritten to the record + ?modal=true, restored on close, reload reopens the modal |
pickers (multiSelect, returnsSelection, context, selectMode, …) and lists narrowed by a parent record opened from a tile, widget or action (route allowed with rewriteUrl: false) |
A LIST ROW always opens its record this way — a record without an editable form gets a read-only *-detail that embeds the narrowed list (lists:) |
never what a list row click opens |
Requirements: target uses NoerdDetail/NoerdPage (or NoerdList for record-lists), a named Route::livewire('{app}/{entity}/{modelId}', …) exists, every identity argument is a route parameter |
Always keep the component as fallback — Noerd::modalFor($route, $component, $args) in PHP;
in YAML/properties pair route: + modalComponent:, $detailRoute + $detailComponent,
newRoute: + newComponent:. The route wins when registered; the component opens when the owning
module is not installed.
Where route: is available: list $detailRoute, list header action route:, detail action
route:, relation-box tile / widget route:, list column type: relation_link, relation field
detailRoute:, navigation modalRoute: / newRoute:, page/detail tab modalRoute:, dashboard
card route=.
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.
- 1mo ago Changed c86eae3798e6
- 1mo ago Changed · +1 lines 2af745c2525a
- 1mo ago Changed · +1 lines d3c0473db212
- 1mo ago First seen · 108 lines · 153 tokens per session scan A 55327c8e3b7f
noerd-modal-development is a skill published in the GitHub repository noerd-dev/noerd (17 stars, last pushed 5d ago), licensed MIT. It adds 153 tokens to every session and 1,601 once invoked, about $0.0006 per session on Opus 5.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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…