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-detail-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-detail-development)<a href="https://agentmods.dev/skills/noerd-dev/noerd/noerd-detail-development"><img src="https://agentmods.dev/badge/skills/noerd-dev/noerd/noerd-detail-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-detail-development"><img src="https://agentmods.dev/badge/skills/noerd-dev/noerd/noerd-detail-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.00142 | $0.01999 |
| Opus 5.5 | $0.00057 | $0.00800 |
| Sonnet 5.5 | $0.00028 | $0.00400 |
| Haiku 4.5 | $0.00014 | $0.00200 |
Grade A, and why
noerd-detail-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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Noerd Detail & Page Development
A Noerd detail is a Livewire single-file component using the NoerdDetail trait, configured by a
detail YAML that is a pure model form. Everything around the form (tabs of a page, relation box,
widgets, embedded detail) is a page (NoerdPage). The hard rules live in the noerd/noerd Boost
guideline; this skill is the procedure. Docs: vendor/noerd/noerd/docs/detail-view.md,
page-view.md, field-types.md, relation-field-types.md, relation-forms.md, themes.md.
1. Decide the shape
| Need | Build |
|---|---|
| Plain record form | *-detail (slim, no methods) |
| Form + relation box / widgets / page tabs / quick-create | *-page with detail: in the page YAML embedding the slim *-detail |
| Fields that edit a related model (e.g. default address) | Keep the detail slim; declare relationForms() on the MODEL (DeclaresRelationForms) |
| Persist through a service | Override store(): validateFromLayout() → service → storeProcess($model) |
| Tenant-singleton settings screen | *-page with the NoerdSettingsPage trait + settings/{name}.yml — stacked full-width fields, may edit several models via $settingsModels; see docs/settings-page.md |
2. Create the detail — resources/views/components/{entity}-detail.blade.php
Singular name, directly in components/. Reference: src/Commands/stubs/resource/detail.blade.stub.
<?php
use Livewire\Component;
use Noerd\Traits\NoerdDetail;
use Vendor\Module\Models\Thing;
new class extends Component {
use NoerdDetail;
public $detailModel = Thing::class; // mandatory
public ?string $detailPrimary = 'thingId'; // mandatory, literal default, binds $modelId to the URL
}; ?>
<x-noerd::page>
<x-slot:header>
<x-noerd::modal-title>{{ __('Thing') }}</x-noerd::modal-title>
</x-slot:header>
<x-noerd::tab-content :layout="$pageLayout" :modelId="$modelId" />
<x-slot:footer>
<x-noerd::delete-save-bar :showDelete="isset($modelId)"/>
</x-slot:footer>
</x-noerd::page>
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 · +5 lines 67377b68e785
- 1mo ago Changed · +3 lines 98aeb899871a
- 1mo ago Changed c8777d8796ef
- 1mo ago First seen · 148 lines · 142 tokens per session scan A 63c65d1d09fc
noerd-detail-development is a skill published in the GitHub repository noerd-dev/noerd (17 stars, last pushed 5d ago), licensed MIT. It adds 142 tokens to every session and 1,999 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…