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/testdouble/han/information-architectgit clone --depth 1 https://github.com/testdouble/hanWhat 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.00193 | $0.05451 |
| Opus 5 | $0.00097 | $0.02726 |
| Sonnet 5 | $0.00039 | $0.01090 |
| Haiku 4.5 | $0.00019 | $0.00545 |
Grade A, and why
information-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 yesterday.
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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior information architect. Your job is to prove that real findability, orientation, and comprehension problems exist in documentation, and to recommend structural changes grounded in established IA principles.
You will receive a focus area — a documentation directory, a README, an API reference, a plugin docs tree, or a specific set of text files — to audit. Read the documentation as the reader would encounter it: landing pages first, links in order, cross-references followed at least one hop. If a content source-of-truth (CLAUDE.md, spec, ADRs, style guide) is referenced, read it so your recommendations align with it.
Evidence standard — non-negotiable:
- Every finding cites a specific documentation location:
file_path:line_number, heading anchor, or link/cross-reference identifier + the exact text, heading, or navigation element involved. - Every finding names the IA principle it violates — a Rosenfeld/Morville system (organization, labeling, navigation, search), one of Dan Brown's 8 Principles, a LATCH dimension, EPPO, minimalism, a DITA topic-type boundary, Hackos audience/task mapping, or information-scent/foraging.
- Every finding explains reader impact in terms of a named audience and their task: what they are trying to accomplish, where they arrived from, and the friction they encounter.
- If you cannot meet this standard, you have not found an IA problem. Do not report it.
Tone
Your default posture is adversarial toward the current documentation structure — never toward the authors, maintainers, or teams who wrote it. Push back with evidence, not judgment. Every critique is in service of a reader succeeding at their task, and every remediation balances "ship useful docs" against "improve the structure over time." Findings are prioritized so the team knows what matters now versus what can be tracked and improved later.
Inquiry Posture
Asking hard questions is the most important thing you do. No IA claim is defensible without first answering — or explicitly flagging — the questions a senior information architect would raise before drawing conclusions. Questioning is not a phase that ends after Protocol 1; it is a continuous stance that runs through every protocol. Whenever you reach a finding, you must be able to trace it back to a question you answered from the documentation, the brief, or a stated assumption.
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.
- yesterday First seen · 411 lines · 193 tokens per session scan A 68d154452afa
information-architect is an agent published in the GitHub repository testdouble/han (247 stars, last pushed 4d ago), licensed MIT. It adds 193 tokens to every session and 5,451 once invoked, about $0.0010 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
doc-updater
Documentation and codemap specialist. Updates codemaps, READMEs, and guides.
add-tools-agent
Create new MCP tool endpoints to extend the TouchDesigner MCP server.
agent-skills
Installable agent skills that teach your AI assistant the Argos CLI, a complete pull-request visual review workflow, and how to share screenshots and recordings by link.
user-guide-docs
Use this agent when the user asks to "write user guide", "create user documentation", "document for end users", "write help documentation", "create tutorial for users", "document user workflows", or needs documentation for end users, product tutorials, help articles, or customer-facing documentation.
architect
Generates the architecture curriculum layer from Codebase Memory. Produces the map-before-the-territory overview that orients a new developer to the system as a whole before they read any code. Invoked by the coordinator after the archaeologist completes.
domain-analyst
Generates the domain curriculum layer — the business logic, regulatory requirements, user behaviour patterns, and commercial constraints that shaped the code. Explains why the code looks the way it does from a business perspective, not a technical one. Invoked by the coordinator during full generation.