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 dkadts/landing-kit-building --skill blocksgit clone --depth 1 https://github.com/dkadts/landing-kit-buildingWrote 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/dkadts/landing-kit-building/blocks)<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/blocks"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/blocks.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.00035 | $0.00593 |
| Opus 5 | $0.00017 | $0.00296 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
blocks 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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/blocks
Walks the checklist from brief/07-interactive.md. For every checked block — fills the corresponding brief/blocks/<block>.md.
When to use
- After
/brief(when07-interactive.mdis checkbox-filled). - Before
/build(all configs must exist for assembly). - When adding a new block to an existing project.
Process
Step 1. Read 07-interactive.md
Find every [x] block. Skip [ ] — not needed.
Step 2. For each checked one — walk 11 sections
Common template (see brief/blocks/README.md):
- Is this block needed → already
[x], confirm. - Trigger / placement.
- Fields / content.
- Validation.
- Where it's sent.
- Success flow.
- Error flow.
- Analytics.
- Accessibility.
- Mobile specifics.
- Priority.
For each — ask one question at a time, use options from the corresponding brief/blocks/*.md as a starting point.
Step 3. Specifics for the main block — contact-form
This is the main CTA, requires extra care:
- Ask about backend (see
brief/06-technical.md→ Email backend). - Confirm recipient (manager email).
- Confirm thank-you flow.
- Confirm UTM handling.
Step 4. Sanity check
After filling all blocks:
- Look for conflicts (e.g. cookie-banner checked but no analytics — why cookie then?).
- Check priorities: too many must-haves? Warn.
- Check mobile specifics: if mobile-first — every block must be touch-friendly.
- Check a11y: every interactive keyboard-accessible?
Step 5. Save + report
Update all brief/blocks/*.md.
Show the user a summary: N blocks configured, M blocks are must-haves.
Rules
- Do not pull in extras. If the user checked chat but can't dedicate an operator — suggest dropping it or replacing with "via form".
- Always clarify backend for forms. Without a clear endpoint the form is useless.
- Show implementation examples. Not "should we autoplay?" but "autoplay after 30s is usually annoying; recommend no".
What NOT to do
- Do not create blocks not in 07-interactive.md.
- Do not "improve" — stick to what's checked.
- Do not skip block sections — all 11 are needed for
/build.
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.
- 6d ago First seen · 75 lines · 35 tokens per session scan A feb52f064ee1
blocks is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 18d ago), licensed MIT. It adds 35 tokens to every session and 593 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
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
regenerate-api
Regenerate the AppointMe frontend API client (orval/TanStack Query hooks + TypeScript schemas) after the backend OpenAPI surface changes. Use this whenever backend endpoints, request/response DTOs, or other contract-affecting types are added, removed, or modified — e.g. after editing files under src/AppointMe.Api…
frontend-design
Visual and UX design quality for interfaces: hierarchy, spacing rhythm, typographic scale, a restrained color system, layout composition, and polished states. The taste layer above frontend architecture and a11y.
a11y
Frontend accessibility audit (WCAG): semantic HTML, keyboard access, focus management, contrast, ARIA, screen readers. Use when building or changing UI, or before shipping a user-facing screen.
frontend
Stack-agnostic frontend discipline (web · mobile · desktop): component structure, state, data fetching, loading/empty/error states, i18n, accessibility, performance. frontend-expert-csk applies it on every stack.
vercel-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.