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 commands/rajconnects/founder-stack/frontend-buildgit clone --depth 1 https://github.com/rajconnects/founder-stackWhat 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.00052 | $0.00940 |
| Opus 5 | $0.00026 | $0.00470 |
| Sonnet 5 | $0.00010 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
frontend-build 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 yesterday.
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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the frontend specialist build step.
Arguments: $ARGUMENTS
Steps
-
Resolve scope. Parse
$ARGUMENTS. Scope is required — there is noauto. If empty, fail loudly:frontend-build requires an explicit scope. Example: /frontend-build OnboardingForm. -
Compute the scope slug. Lowercase, alphanumerics + dashes only. Same slugification as
/ux-wireframeand/ux-mockup. -
Hard gate on design approval. Check for
.claude/.design-approved-<scope-slug>.- If present: continue with
approval_state = approved. - If missing AND
--bypassis NOT set: fail with verdictBLOCKED_NO_DESIGN_APPROVAL. Print the exact remediation: "Run /ux-wireframe then /ux-mockup and approve. Or pass --bypass if this is an emergency (will be flagged in handoff)." Stop. Do not launch the agent. - If missing AND
--bypassIS set:touch .claude/.design-bypass-<scope-slug>(consumed by/handoffand/design-gate). Print: "⚠ Design approval bypassed for . This will be surfaced in /handoff." Continue withapproval_state = bypassed.
- If present: continue with
-
Resolve config and inline. Read
.claude/project.jsononce. Extract:design_system.components_spec,design_system.flow_spec,design_system.tokens,design_system.figma.file_key,design_system.figma.screens,stack.frontend,stack.frontend_root,test_roots.frontend,test_commands.frontend. Ifstack.frontendis null, fail:frontend-build only runs for frontend stacks (stack.frontend is null).Iffrontend_rootis null, fail likewise. -
Launch
frontend-engineerwith a self-contained prompt containing: scope label and slug, the inlined config fields above, andapproval_state. Do NOT ask the agent to re-readproject.json. Do NOT ask the agent to write files — that is your job. -
Print the agent output verbatim. Including the brief sections (composition, optimization, scaffold body). Do not soften or reinterpret.
-
Write the scaffold (or skip). Parse the agent output:
- Extract the File path from the agent header.
- Extract the scaffold body from the
## (c) Scaffold bodycode fence. - If file at the resolved path exists: print "File exists at
<path>— emitting brief only. No scaffold written." Do not write. Do not ask. Continue cleanly. - If file does not exist: ask the operator: "Write scaffold to
<path>? (yes/no)". Onyes, Write the scaffold body to that path. Onno, skip.
-
Closing line. On success print: "Brief delivered. Implement against
<test-path>(red tests). Run/design-gate <scope>before/handoff."
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.
- yesterday First seen · 42 lines · 52 tokens per session scan A 4694f057a35e
frontend-build is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 940 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.