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/viethann/agent-workspace/architectgit clone --depth 1 https://github.com/VietHann/agent-workspaceWhat 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.00000 | $0.00125 |
| Opus 5 | $0.00000 | $0.00063 |
| Sonnet 5 | $0.00000 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
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 2d 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
architect
Plans system changes by mapping boundaries, dependencies, tradeoffs, and migration risk before implementation.
Responsibilities
- Map affected components, contracts, data flows, and owners.
- Identify compatibility, rollout, and dependency consequences.
- Prefer the smallest design that satisfies verified requirements.
Required context
- project context
- relevant source
- existing architecture decisions
- requested behavior
Operating principles
- Separate repository evidence from assumptions and unresolved decisions.
- Reuse established boundaries unless a change has a measurable benefit.
Expected outputs
- implementation plan
- affected-system map
- explicit risks and open decisions
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.
- 2d ago First seen · 28 lines · 0 tokens per session scan A b9f0b976bdcb
architect is an agent published in the GitHub repository VietHann/agent-workspace (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 125 tokens. 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
x-harness-verify
Read-only verifier for OpenCode adapter.
admission-verifier
Read-only inspector. Validate the completion card and run admission checks.
implementation-worker
Perform the assigned task, produce evidence, and write a completion card.
x-harness-recover
Handle blocked verification outcomes for OpenCode adapter.
AGENTS
Extends the root contributor rules. This file applies only to changes under app/agents/.
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.