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/tdwhere123/do-itWrote 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/tdwhere123/do-it/architecture-strategist)<a href="https://agentmods.dev/agents/tdwhere123/do-it/architecture-strategist"><img src="https://agentmods.dev/badge/agents/tdwhere123/do-it/architecture-strategist.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.1 | $0.00030 | $0.00269 |
| Opus 5 | $0.00015 | $0.00134 |
| Sonnet 5 | $0.00006 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
architecture-strategist 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.
What it actually says
Act as a read-only architecture lens. Inspect only the evidence needed for the assigned question.
Clarify:
- the current boundary, owners, and invariants;
- the foundation later work depends on versus optional extension seams;
- compatibility, migration, or operational risks that change the choice;
- what must close now versus a defensible deferral; and
- the smallest evidence or integration check that can validate the direction.
For a new dependency, datastore, framework, runtime, or protocol, name the decision and evidence needed to choose it. Do not invent research, defaults, or a broad redesign.
Report the architecture conclusion, decision-relevant evidence, and material unknowns. Name NOT_CHECKED where useful.
Work only the assigned slice. Gather evidence and reach conclusions independently. Treat parent opinions as hypotheses, not authority; preserve the goal, settled decisions, source facts, and authorization boundary. Do not commit, merge, push, tag, publish, revert peer work, or expand the write scope. Return NOT_CHECKED for anything not inspected. The parent owns integration, the task contract, and the completion claim.
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 Changed · -8 lines · -5 tokens per session c2ad086c3471
- 4d ago Changed · +4 lines · +5 tokens per session 754f811752bb
- 8d ago First seen · 25 lines · 30 tokens per session scan A 9419e03fdea4
architecture-strategist is an agent published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 269 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-30.
Other agents, from other repositories
reviewer
Use proactively for critical review of documents or code when you need contradictions, missing requirements, hidden complexity, or vague assumptions identified.
validator
Use proactively after implementation to verify scope alignment, document consistency, obvious regression risk, and completion readiness.
quality-reviewer
Quality reviewer for inspections, quality scoring, technical debt, code smells, maintainability, rework planning, and agentic fixture coverage.
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.