An interactive questionnaire that collects a project's requirements in nine brief files, starting with whether the design should prioritize desktop or mobile screens.

Use it when starting a project, revising an existing brief, or choosing details such as the target niche, device priority, and content process.

It turns unspecified decisions into recorded answers before implementation, so later work has clear guidance about the audience, content, goals, and layout.

brief — Skill for Claude Code by dkadts

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 dkadts/landing-kit-building --skill brief

Clone the repo

git clone --depth 1 https://github.com/dkadts/landing-kit-building

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dkadts/landing-kit-building/brief/github.svg)](https://agentmods.dev/skills/dkadts/landing-kit-building/brief)

Your own site

<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/brief"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/brief/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/brief"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 644 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.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.00644
Opus 5	$0.00020	$0.00322
Sonnet 5	$0.00008	$0.00129
Haiku 4.5	$0.00004	$0.00064

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

Security

Grade A, and why

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

.claude/skills/brief/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/brief

Guides the user through the questionnaire. Fills brief/00-priority.md → brief/08-content-pipeline.md.

When to use

Start of a new project (before any /build).
User prefers a dialog over filling .md files by hand.
Revising an existing brief.

Process

Step 1. Read existing files Read every brief/*.md. Determine which fields are filled, which are TBD.

Step 2. Ask the first — most important — question

Desktop-first or mobile-first?

This decides:
- Assembly order (down or up)
- Block composition
- Reference viewport (1920px or 390px)

Help to choose: <brief decision table from 00-priority.md>

Wait for an explicit answer. Save to brief/00-priority.md.

Step 3. Walk files 01-08 in order

For each file:

List TBD fields.
Ask one question at a time (do not batch 10 questions at once — user tires).
Use checklists where preset options exist.
Save the answer (Edit tool).

Step 4. Special attention — niche discovery

brief/01-business.md — niche section — critical for /copy-analyze. Do not accept "beauty" — narrow it to "men's Botox for CEOs 35-50 in Barcelona". Do not accept "clients" — narrow maturity (cold/warm/hot).

Step 5. After 07-interactive

If the user checked interactive blocks — offer to run /blocks immediately to configure.

Step 6. Final summary

Show brief completeness: how many fields LOCKED, how many TBD. If TBD remain — what to ask the client.

Rules of behavior

One field — one question. Do not batch.
Do not guess for the user. If unclear — clarify.
Use examples. "e.g. form submission → manager calls within 2 hours".
Save as you go. Not at the end. Otherwise if the session drops — everything's lost.
Respect status. If a field is already filled — do not re-ask, only clarify if needed.

What NOT to do

Do not start /design-lock until 01-business + 02-audience + 05-design are filled.
Do not suggest skipping 00-priority — it's critical.
Do not fill brief/copy-analysis.md — that's /copy-analyze.
Do not touch brief/blocks/*.md — that's /blocks.

Read the full file on GitHub · 79 lines

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.

9d ago First seen · 79 lines · 41 tokens per session scan A 240c3c7ce1d6

Subscribe to this mod's changes

brief is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 20d ago), licensed MIT. It adds 41 tokens to every session and 644 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.

Planning ai-agents ai-agents-automation anthropic anti-slop boilerplate boilerplate-template

next-upgrade

Upgrade Next.js to the latest version following official migration guides and codemods.

agustinusnathaniel/nextarter-tailwind · 19 tokens

deploy

Ship a build reversibly — to a host you manage or a platform that manages it. Pick the topology first, keep the previous version reachable, gate on health, roll back without rebuilding. Use when shipping anywhere users can reach.

byerlikaya/claude-starter-kit · 50 tokens

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…

bravodev-hub/appointme · 136 tokens

brief