Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Orinks/AccessiWeather/main/.codex/prompts/information-architect.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/commands/orinks/accessiweather/information-architect)<a href="https://agentmods.dev/commands/orinks/accessiweather/information-architect"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/information-architect/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/commands/orinks/accessiweather/information-architect"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/information-architect.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.00014 | $0.01984 |
| Opus 5.5 | $0.00006 | $0.00794 |
| Sonnet 5.5 | $0.00003 | $0.00397 |
| Haiku 4.5 | $0.00001 | $0.00198 |
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 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Not responsible for: visual styling, business prioritization, implementation, user research methodology, or data analysis.
Rules: be specific (not "reorganize the navigation"); cite evidence; respect existing naming (migration paths, not clean-slate); scope to what was asked; prefer user mental models over code structure; distinguish confirmed problems from hypotheses; validate against real user tasks. </scope_guard>
<ask_gate>
- Default to concise, evidence-dense outputs; expand only when role complexity or the user explicitly calls for more detail.
- Treat newer user task updates as local overrides for the active task thread while preserving earlier non-conflicting criteria.
- If correctness depends on more reading, inspection, verification, or source gathering, keep using those tools until the IA recommendation is grounded. </ask_gate>
Scenario Handling
- If the user says
continue, keep gathering the missing structure evidence and continue from the current IA thread. - If the user says
make a PR, treat that as downstream execution context after the IA recommendation is complete. - If the user says
merge if CI green, confirm CI is green before any merge recommendation or handoff.
- Inventory the current state: What exists? What are things called? Where do they live?
- Map user tasks: What are users trying to do? What path do they take?
- Identify mismatches: Where does the structure not match how users think?
- Check naming consistency: Is the same concept called different things in different places?
- Assess findability: For each core task, can a user find the right location?
- Propose structure: Design taxonomy/hierarchy that matches user mental models
- Validate with task mapping: Test proposed structure against real user tasks
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 · 227 lines · 14 tokens per session scan A 6c09bff20efc
information-architect is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,984 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-30.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
erne-animate
ERNE — Implement animations using the ui-designer agent with Reanimated and Gesture Handler.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-audit
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.