Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/event4u-app/agent-confignpx agentmods add skills/event4u-app/agent-config/blade-uiWrote 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/event4u-app/agent-config/blade-ui)<a href="https://agentmods.dev/skills/event4u-app/agent-config/blade-ui"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/blade-ui.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.1 | $0.00042 | $0.01647 |
| Opus 5 | $0.00021 | $0.00823 |
| Sonnet 5 | $0.00008 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
blade-ui 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 8d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blade-ui
Grounded stack guidance: pull idiomatic Do/Don't + docs URLs from the adopted stack corpus before improvising —
./scripts-run <skills-root>/corpus-grounding/scripts/ground search --manifest <skills-root>/design-intelligence/data/manifest.json --stack laravel "<topic>"(thelaravelstack file is Blade/UI-scoped, not general Laravel). Seedesign-intelligence.
Positioning — dispatched, not standalone
blade-ui is the apply-step executor for the Blade stack. It is
invoked by directives/ui/apply.ts
once the design brief is locked, and revisited by review.ts /
polish.ts during the design-review loop. It does not own the
flow, does not drive the audit, and does not lock the design.
| Concern | Owner |
|---|---|
| Audit + token inventory (mandatory pre-step) | existing-ui-audit |
| Design brief (layout / states / microcopy) | directives/ui/design.ts |
| Universal design heuristics | fe-design |
| Review + polish loop | directives/ui/review.ts + polish.ts |
When to use
Cite this skill when:
state.stack.frontend == "blade"(or the project is clearly Blade-only without Livewire / Flux) anddirectives/ui/apply.tsdispatches to this skill- Editing or creating Blade views, components, partials, layouts, or forms
Do NOT use when:
- API-only endpoints (use
api-endpointskill) - Livewire components (use
livewireskill — it composes Blade views internally) - Flux UI components (use
fluxskill) - Driving the full UI flow yourself — that is the
directives/ui/orchestrator
Procedure: Create Blade view or component
Step 0: Inspect
- Confirm Blade is used — check
resources/views, components, layouts. - Inspect existing UI patterns — layouts, partials, component naming, CSS conventions.
- Check form handling style — old input, validation errors, session flashes, reusable field partials.
- Inspect neighboring templates — match indentation, directives, slot usage, classes.
- Determine data flow — what belongs in controller/view model vs. template.
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.
- 8d ago First seen · 157 lines · 42 tokens per session scan A 7c0bcc670433
blade-ui is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,647 once invoked, about $0.0002 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
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…
threejs-geometry
Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
Error Boundary Tester
Validate error boundary implementations in React and other frameworks ensuring graceful degradation, proper fallback UI rendering, and error recovery flows.
react-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes. Do NOT…
error-handling
When adding error boundaries, handling async errors, or building error UI states.