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 ZachArticulateV/designer-pro-and-seo --skill blast-promptgit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/blast-prompt)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/blast-prompt"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/blast-prompt/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/zacharticulatev/designer-pro-and-seo/blast-prompt"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/blast-prompt.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.00093 | $0.00734 |
| Opus 5 | $0.00046 | $0.00367 |
| Sonnet 5 | $0.00019 | $0.00147 |
| Haiku 4.5 | $0.00009 | $0.00073 |
Grade A, and why
blast-prompt 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blast-prompt
Family: build-and-qa Status: Stable
Purpose
Produce a structured, complete build brief in BLAST format so a build agent (Claude Code, Cursor, etc.) can one-shot a high-quality build. Five sections, each with a required-fields checklist so nothing is forgotten before launch:
- Blueprint — what's being built (pages, sections, features, audience, fidelity)
- Link — integrations & external dependencies (forms, payments, analytics, CRM)
- Architect — stack, file structure, data flow, performance budget
- Stylize — design system reference (palette, type, effects, anti-patterns)
- Trigger — the actual paste-ready command for the build agent
Triggers
- "blast prompt" / "build brief"
- "structured build prompt" / "complete build prompt"
- "brief for the build agent"
- "prompt I can paste into Claude or Cursor"
Inputs
- Project goal (one sentence)
- Stack preference (or "agent picks")
- Existing design system (or "generate one")
- Integrations needed
- Target deployment
Steps
- Load the template
templates/blast-template.md. - Walk each section with the user, filling required fields. Auto-fill from
project context where possible (CLAUDE.md, an existing design system /
design-system/MASTER.md). - Pull the Stylize section from a
design-system-genresult (run it first if no design system exists). Map palette hex, typography, and effects into the slots. - Validate completeness. Run the template's completeness gate — every required field filled, no "TBD". For integrations and secrets, list names only, never secret values.
- Write the Trigger. Compose a single, self-contained, paste-ready launch command that references the four sections above so the build agent has full context in one paste.
- Render both a Markdown brief and a plain-text version for CLI paste. Offer
to launch directly or hand off to
parallel-buildfor multi-variant builds.
Outputs
- Markdown brief in BLAST format (from the template)
- Plain-text version for paste-into-CLI
- A completeness gate confirming the brief is launch-ready
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.
- 12d ago First seen · 71 lines · 93 tokens per session scan A ce38f09c3558
blast-prompt is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 734 once invoked, about $0.0005 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
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…
engineering-onboarding
Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…