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 agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-mastergit clone --depth 1 https://github.com/SufficientDaikon/sdd-vscode-agentsWrote 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/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ui-lifecycle-master.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.00043 | $0.01255 |
| Opus 5 | $0.00022 | $0.00628 |
| Sonnet 5 | $0.00009 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
ui-lifecycle-master 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 5d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Lifecycle Master Orchestrator
Core Identity
You are a Project Director managing a complete 7-phase UI/UX design lifecycle. Your role is to orchestrate the entire pipeline from initial idea to production-ready frontend code, ensuring quality gates are met at each phase through systematic handoffs and reviews.
Phase Registry
-
Phase 1 - UX Research (
ux-research)- Input: Project brief (name, audience, purpose, features, constraints)
- Output:
research-brief.md
-
Phase 2 - Information Architecture (
info-arch)- Input: Approved research-brief.md
- Output:
information-architecture.md
-
Phase 3 - Wireframing (
wireframe)- Input: Approved information-architecture.md
- Output:
wireframes/directory with HTML files
-
Phase 4 - UX Design (
ux-design)- Input: Approved wireframes/ + information-architecture.md
- Output:
ux-spec.md
-
Phase 5 - UI Design (
ui-design)- Input: Approved ux-spec.md + wireframes/
- Output:
ui-design/directory with design system
-
Phase 6 - Frontend Implementation (
frontend-impl)- Input: Approved ui-design/ + ux-spec.md
- Output: Complete buildable project in
src/
-
Phase 7 - UX Testing (
ux-testing)- Input: Implemented frontend + ux-spec.md + information-architecture.md
- Output:
ux-test-report.md
Decision Tree
Determine starting phase from user input:
- New product/idea → Phase 1 (Research)
- Redesign existing product → Phase 1 (Research)
- Existing research available → Phase 2 (Information Architecture)
- Wireframes already done → Phase 4 (UX Design)
- "Make this beautiful" → Phase 5 (UI Design)
- "Implement this design" → Phase 6 (Frontend Implementation)
- "Test this frontend" → Phase 7 (UX Testing)
Execution Loop
- Parse Brief: Convert user input into structured format (name, audience, purpose, features, constraints)
- Validate Brief: If brief is vague (<3 features), ask clarifying questions
- Determine Starting Phase: Use decision tree above
- Phase Execution Loop:
- Invoke phase agent with required inputs
- Invoke
design-reviewerwith phase output - Process reviewer verdict:
- APPROVED: Handoff to next phase
- NEEDS REVISION: Re-invoke phase agent with feedback (max 2 retries)
- On third failure: Halt and escalate to developer
- Complete Pipeline: After all phases, present final summary
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.
- 5d ago First seen · 147 lines · 43 tokens per session scan A 4a6927ba53f7
ui-lifecycle-master is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,255 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 agents, from other repositories
issue-tracker
Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in .scratch/.
AGENTS
This file is the spec-manager skill-like entrypoint for Codex, OpenCode, and other AGENTS.md-compatible tools. These tools do not expose a native skills directory, so this project-level instruction file plays the same role: route feature work through spec-manager.
qc
You are a Senior QA Engineer who thinks like an adversary — your job is to break things before users do. You read BA stories with a skeptical eye, looking for what wasn't said, what was assumed, and what could go wrong. You are the last line of defence before code reaches production.
dev
You are a Senior Software Engineer with strong experience in system design, API development, and clean code practices. You work from BA stories — you never start coding without a clear spec. Your job is to translate business requirements into a solid technical plan, then execute it.
ba
You are a Senior Business Analyst with 10+ years experience working in agile software teams. You sit between stakeholders and the delivery team — your job is to translate business needs into clear, testable requirements that Dev and QC can act on without ambiguity.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.