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 agentmods add skills/ytvee-dev/webdev-agent-kit/greenfield-project-buildernpx skills add ytvee-dev/webdev-agent-kit --skill greenfield-project-buildergit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWhat 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 | $0.00048 | $0.01953 |
| Opus 5 | $0.00024 | $0.00977 |
| Sonnet 5 | $0.00010 | $0.00391 |
| Haiku 4.5 | $0.00005 | $0.00195 |
Grade A, and why
greenfield-project-builder 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 2d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Greenfield Project Builder
Purpose
Plan and execute the first safe steps of a new frontend project without turning a vague product idea into uncontrolled scaffolding.
This skill converts a product idea into a minimal frontend project plan, explicit stack assumptions, approval gates, first vertical slice, and onboarding handoff. It must not scaffold, install packages, or create application files unless the user explicitly approves the exact action.
When To Use
Use this skill only for Deep Workflow tasks.
Use this skill when the user asks to:
- start a new frontend project;
- plan a new frontend app from a product idea;
- create a project structure before scaffolding;
- define the first vertical slice of a new app;
- choose an intended frontend stack before project creation;
- prepare onboarding overlays for an empty or new project;
- turn a broad product concept into a small frontend implementation path.
When Not To Use
Do not use this skill for:
- existing-project bugfixes;
- one route or component in an existing project;
- purely visual redesign of an existing screen;
- refactoring existing code;
- UI component library setup;
- testing workflows;
- backend, database, ORM, migrations, infrastructure, or production systems;
- package installation by default;
- automatic scaffolding without approval.
Do not use this skill when frontend-architecture-planner is enough for an existing project.
Required Context
- Read
AGENTS.md. - Read
common/prompt-intent-routing-rules.md. - Confirm the task is
Deep Workflow. - Read
common/framework-adaptation-policy.mdandcommon/build-tool-boundary-rules.md. - Read the compact goal contract or
project/active-goals.mdwhen present. - Read the compact execution plan or
project/active-plan.mdwhen present. - Read existing project overlays only when this is a new app inside a larger existing workspace:
project/stack-profile.md;project/architecture-map.md;project/build-profile.mdwhen present;project/workspace-profile.mdwhen present;project/verification-profile.mdwhen present.
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.
- 2d ago First seen · 226 lines · 48 tokens per session scan A 7351cff3009c
greenfield-project-builder is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,953 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
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
shipping-reproducible-results
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
actions-reusable-workflows
Wire a repository to the bitwise-media-group/github-workflows reusable workflows — thin, SHA-pinned caller workflows for CI, security (CodeQL) scanning, release (release-please/GoReleaser/Zensical docs), the signature-preserving fast-forward /merge + merge-review-ack + merge-notice flows, and add-to-project — plus the…
go-style
Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…
workflow-skill-evals
Write the evolve evaluation suite for an agent skill: its triggers (triggers.json — Tier 1 activation tests) and behavioral evals (evals.json — Tier 2 task tests), under evals/ /. Use when asked to generate, write, author, scaffold, or balance an eval suite, evals, or triggers for a skill; to create or edit a…