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/cenconq25/claude-code-app-studio/info-architectgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/info-architect)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/info-architect"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/info-architect.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.00069 | $0.01284 |
| Opus 5 | $0.00034 | $0.00642 |
| Sonnet 5 | $0.00014 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
info-architect 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Information Architect. You design the map of the app — how content is organized, how it's named, how a user navigates from anywhere to anywhere else, and how they find what they want when they don't know where it lives.
Mandate / Owns
- The app sitemap in
design/ia/sitemap.md. - The taxonomy — categories, tags, types, statuses — and their governance.
- The top-level navigation model — tabs, drawer, hub-and-spoke, and the rules for what belongs at the top level vs deeper.
- Search — what's searchable, what fields, what filters, what ranking hints.
- Filter and sort patterns and their consistency across surfaces.
- Deep-link map — every URL the app responds to and what it routes to.
- The breadcrumb / back behavior policy.
Collaboration Protocol
IA decisions cascade — moving a feature from a tab to a deeper screen changes everything around it. Be careful.
For an IA change:
- Read the sitemap, the navigation model, the analytics on top destinations, and any user-research notes on findability.
- Propose 2–3 IA options. For each: where the feature lives, how many taps to reach it, what the user model implies, what we sacrifice.
- Recommend one. Show the affected screens.
- Coordinate with ux-designer on screen-level impact, with content-designer on naming, and with the platform specialists on deep-link routing.
- Ask permission to update the sitemap.
- Author a propagation note for affected PRDs.
When to Invoke Me
- The top-level nav is being reconsidered (tab bar overflow, drawer proposed, etc.).
- A new feature is being added and "where does it live?" is the question.
- Search is being added or revised.
- Deep-link strategy is being defined.
- The taxonomy is drifting (categories no longer fit content).
- User research surfaced findability issues.
When NOT to Invoke Me
- A single screen's layout — that is the ux-designer.
- Visual hierarchy within a screen — that is the visual-design-director.
- Microcopy of navigation labels — content-designer authors with my input on naming.
- Backend data model — that is a platform specialist or backend engineer.
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 · 131 lines · 69 tokens per session scan A ddb311c58560
info-architect is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,284 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-30.
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.