apply-frontend-blueprint

apply-frontend-blueprint is a skill for Codex from barrosohub/frontend-stack-blueprint. It costs 67 tokens per session (625 once invoked), scanned A, original, MIT.

A process for applying or checking a documented frontend technology plan in a software project. The plan records which tools and design choices the project should follow, along with evidence and exceptions.

In plain words
What is it for?
Use it to inspect a repository, choose supported frontend profiles, create or update blueprint.config.json, run conformance checks, plan changes, and verify implementation evidence.
Why use it?
It helps prevent frontend changes that conflict with the project’s requirements or chosen technology. It also shows what is missing before work begins and checks whether the implementation follows the plan.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to inspect a repository, choose supported frontend profiles, create or update blueprint.config.json, run conformance checks, plan changes, and verify implementation evidence.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint
Install

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.

Any agent
npx skills add barrosohub/frontend-stack-blueprint --skill apply-frontend-blueprint
Clone the repo
git clone --depth 1 https://github.com/barrosohub/frontend-stack-blueprint

Made for: Codex.

Wrote 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.

agentmods badge for apply-frontend-blueprint

README.md
[![agentmods](https://agentmods.dev/badge/skills/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint/github.svg)](https://agentmods.dev/skills/barrosohub/frontend-stack-blueprint/apply-frontend-blueprint)
Your own site
<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.

agentmods 80×15 button for apply-frontend-blueprint

Your own site · 80×15
<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>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 625 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 95f7587d880f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

skills/apply-frontend-blueprint/SKILL.md · 60 lines

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

  1. Locate the blueprint root and the target project. Read stack.yaml, agent-contract.json, profiles/README.md, and each candidate profile.

  2. Inspect the target repository without writing. Read its agent instructions, package manifest, lockfile, build/test configs, CI, targets, and product docs.

  3. Select core implicitly. 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.

  4. Create or update blueprint.config.json from blueprint.config.example.json. Record only temporary exceptions as waivers; require an ID, reason, owner, and expiry date.

  5. Run the checker before changes:

    node <blueprint>/scripts/check-project-conformance.mjs \
      --project <target> --format json
    
  6. Present an Impact Preflight: selected profiles, evidence, missing requirements, exact files and dependencies affected, commands, risks, and rollback approach.

  7. Apply only authorized changes. Prefer official CLIs after preflight, pin reproducible inputs, preserve unrelated work, and never expose secrets.

  8. Run the project's applicable typecheck, lint, unit, build, browser, security, accessibility, release, and target-specific checks.

  9. 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.md unless 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.

Read the full file on GitHub · 60 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 60 lines · 67 tokens per session scan A 95f7587d880f

Subscribe to this mod's changes

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.

Related

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.

NousResearch/hermes-agent · 20 tokens

pretext

Build creative browser demos with DOM-free text layout.

NousResearch/hermes-agent · 13 tokens

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/CopilotKit · 175 tokens

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/CopilotKit · 46 tokens

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/CopilotKit · 61 tokens

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.

CopilotKit/CopilotKit · 48 tokens