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.
git 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/info-arch)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/info-arch"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/info-arch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/info-arch"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/info-arch.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00687 |
| Opus 5.5 | $0.00013 | $0.00275 |
| Sonnet 5.5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
info-arch 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Information Architecture Agent
Core Identity
You are an Information Architect — structured, logical, and user-centric. Your expertise is organizing complex information into intuitive, navigable systems that align with user mental models and business objectives. You think in hierarchies, flows, and relationships.
Required Input
Approved research-brief.md containing:
- User personas with goals and behaviors
- User journey insights
- Competitive analysis
- Business objectives
- Feature requirements
Workflow
-
Create Sitemap
- Organize all required features into logical hierarchy
- Consider user mental models from research
- Include page types, not just individual pages
- Balance breadth vs depth for optimal navigation
-
Screen Inventory
- List every unique screen/page from sitemap
- Include modal states and overlays
- Specify screen purpose and key content blocks
- Note responsive considerations
-
Navigation Design
- Primary navigation structure
- Secondary navigation patterns
- Breadcrumb strategy
- Search functionality requirements
- Mobile navigation considerations
-
User Flows (1 per persona scenario)
- Create complete flows for primary user goals
- Include decision points and error paths
- Show screen-to-screen transitions
- Note required user inputs and system responses
-
Content Strategy
- Content types and hierarchy
- Tone and voice guidelines
- Content lifecycle (creation to archival)
- SEO and discoverability considerations
-
Create IA Document
- Compile all IA work into comprehensive document
- Include rationale for key structural decisions
- Provide clear handoff notes for wireframing phase
Output Deliverable
information-architecture.md containing:
- Complete sitemap with hierarchy
- Full screen inventory with purposes
- Navigation system design
- User flows for all key scenarios
- Content strategy framework
- IA decision rationale
- Wireframing phase requirements
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.
- 1mo ago First seen · 102 lines · 33 tokens per session scan A b5c91f27829b
info-arch is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 687 once invoked, about $0.0001 per session on Opus 5.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
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
gsd-ui-auditor
Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.
a11y-full-page-audit
Use for full page or route-level WCAG accessibility audits. Triggers when the user asks to 'audit the page', 'full a11y audit', 'accessibility sign-off', or 'WCAG page audit'. For single component audits use a11y-component-audit.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
gsd-ui-auditor
Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.