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 barrosohub/frontend-stack-blueprint --skill apply-frontend-blueprintgit clone --depth 1 https://github.com/barrosohub/frontend-stack-blueprintWrote 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/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint)<a href="https://agentmods.dev/skills/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint"><img src="https://agentmods.dev/badge/skills/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint/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/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint"><img src="https://agentmods.dev/badge/skills/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.00625 |
| Opus 5 | $0.00034 | $0.00313 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
apply-frontend-blueprint 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 9d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Frontend Blueprint
Apply the blueprint as an evidence-backed contract. Keep the target repository's user instructions and explicit product requirements authoritative.
Workflow
-
Locate the blueprint root and the target project. Read
stack.yaml,agent-contract.json,profiles/README.md, and each candidate profile. -
Inspect the target repository without writing. Read its agent instructions, package manifest, lockfile, build/test configs, CI, targets, and product docs.
-
Select
coreimplicitly. Activate optional profiles only when explicit product requirements or repository evidence support them. Ask before proceeding when a materially ambiguous profile changes architecture or installed capabilities. -
Create or update
blueprint.config.jsonfromblueprint.config.example.json. Record only temporary exceptions as waivers; require an ID, reason, owner, and expiry date. -
Run the checker before changes:
node <blueprint>/scripts/check-project-conformance.mjs \ --project <target> --format json -
Present an Impact Preflight: selected profiles, evidence, missing requirements, exact files and dependencies affected, commands, risks, and rollback approach.
-
Apply only authorized changes. Prefer official CLIs after preflight, pin reproducible inputs, preserve unrelated work, and never expose secrets.
-
Run the project's applicable typecheck, lint, unit, build, browser, security, accessibility, release, and target-specific checks.
-
Run conformance again. Report selected and resolved profiles, changed files, verification results, waivers, warnings, and remaining failures.
Selection Rules
- Do not install the full stack. Profiles and capabilities are gates, not a starter dependency list.
- Do not activate
networked-app, production, component-platform, Electron, PWA, authentication, data access, observability, or advanced capabilities by taste. - Do not create a root
DESIGN.mdunless the product has explicit visual intent or source tokens. When active, treat it as the visual contract. - Do not weaken a project-local instruction to satisfy the blueprint silently. Surface the conflict and request direction when it changes the outcome.
- Do not accept permanent waivers. Expired waivers fail conformance.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 60 lines · 67 tokens per session scan A 95f7587d880f
apply-frontend-blueprint is a skill published in the GitHub repository barrosohub/frontend-stack-blueprint (3 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 625 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
p5js
Use when users request: p5.js sketches, creative coding, generative art, interactive visualizations, canvas animations, browser-based visual art, data viz, shader effects, or any p5.js project.
pretext
Build creative browser demos with DOM-free text layout.
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.