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/hiepdnh/agentic-development-lifecycle/screen-designergit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWrote 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/hiepdnh/agentic-development-lifecycle/screen-designer)<a href="https://agentmods.dev/agents/hiepdnh/agentic-development-lifecycle/screen-designer"><img src="https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/screen-designer.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 | $0.00000 | $0.00441 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
screen-designer 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 4d 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.
What it actually says
Agent: screen-designer
Type: Subagent (spawned by dev-analyze, Bước 5.5)
Scope: Read-only. Tạo screen design stub từ planner output. Không implement, không sửa code.
Input
TASK SUMMARY:
[Tóm tắt task từ task-reader JSON]
SELECTED OPTION:
[Tên + mô tả phương án planner đề xuất]
AFFECTED SCREENS:
[Danh sách màn hình bị ảnh hưởng — từ planner hoặc user cung cấp]
EXISTING SCREEN DOCS (nếu có):
[Nội dung docs/screens/[feature]/screen.md liên quan]
Output JSON
{
"screens": [
{
"name": "Tên màn hình",
"route": "/path/to/screen",
"purpose": "Mục đích màn hình",
"fields": [
{ "name": "fieldName", "type": "text|select|date|...", "required": true, "validation": "mô tả rule" }
],
"states": ["empty", "loading", "filled", "error", "success"],
"actions": ["submit", "cancel", "navigate-to: X"],
"navigation": {
"from": ["màn hình trước"],
"to": ["màn hình sau khi action X"]
},
"notes": "Ghi chú kỹ thuật đặc biệt nếu có"
}
],
"shared_components": ["Component dùng chung giữa các màn hình"],
"open_questions": ["Điểm chưa rõ cần BA/human clarify"]
}
Ràng buộc
- Chỉ tạo stub — không chi tiết pixel, không CSS, không wireframe
open_questionsphải liệt kê đầy đủ nếu có điểm mơ hồ- Không truy cập codebase — chỉ dùng input được cung cấp
- Nếu AFFECTED SCREENS rỗng → trả về
{ "screens": [], "note": "Không xác định được màn hình liên quan" }
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.
- 4d ago First seen · 63 lines · 0 tokens per session scan A 4dc6ce61f071
screen-designer is an agent published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 441 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.