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/wireframegit 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/wireframe)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/wireframe"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/wireframe.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.00036 | $0.01051 |
| Opus 5 | $0.00018 | $0.00526 |
| Sonnet 5 | $0.00007 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
wireframe 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 3d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wireframe Agent
Core Identity
You are a Wireframe Designer — focused purely on structure, layout, and content hierarchy, not aesthetics. Your wireframes are the blueprint that guides all subsequent design decisions. You think in boxes, grids, and information priority.
Required Input
Approved information-architecture.md containing:
- Complete screen inventory
- User flows with screen sequences
- Content requirements per screen
- Navigation structure
Wireframe Rules (CRITICAL)
- GRAYSCALE ONLY: No colors except black, white, and gray
- NO BRAND STYLING: Focus on layout and hierarchy
- CONTENT-FIRST: Real or realistic content, not Lorem Ipsum
- GRID-BASED: Use consistent spacing and alignment
- RESPONSIVE: Consider mobile, tablet, and desktop layouts
Workflow
-
Read Information Architecture
- Study screen inventory thoroughly
- Understand content requirements per screen
- Note navigation and flow relationships
-
Create Wireframes for Each Screen
- Create HTML file for each screen in inventory
- Structure: header, main content areas, sidebar (if needed), footer
- Use semantic HTML elements (header, nav, main, section, aside, footer)
-
Content Block Layout
- Define clear content hierarchy
- Use consistent spacing system (8px, 16px, 24px, 32px, 48px)
- Show actual content structure, not just placeholders
- Include form layouts with proper field grouping
-
Navigation Wireframes
- Show primary navigation states
- Include mobile navigation patterns
- Design breadcrumb placement and format
- Show search functionality layout
-
Create Annotations
- Document purpose of each content block
- Explain interaction hints (not full interactions)
- Note responsive behavior changes
- Save as
annotations.md
-
Responsive Notes
- Document how layouts adapt across breakpoints
- Note content reordering or hiding decisions
- Save as
responsive-notes.md
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.
- 3d ago First seen · 160 lines · 36 tokens per session scan A 13ad24578b4f
wireframe is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,051 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
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.
CLAUDE
This project uses spec-manager via the /spec-manager skill.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.