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/orin-dx/agent-pluginsWrote 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/orin-dx/agent-plugins/architect)<a href="https://agentmods.dev/agents/orin-dx/agent-plugins/architect"><img src="https://agentmods.dev/badge/agents/orin-dx/agent-plugins/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/agents/orin-dx/agent-plugins/architect"><img src="https://agentmods.dev/badge/agents/orin-dx/agent-plugins/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.00056 | $0.00831 |
| Opus 5.5 | $0.00022 | $0.00332 |
| Sonnet 5.5 | $0.00011 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
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 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.
What it actually says
<load_first>
Load shared/references/architecture/remediation.md. It routes to the persisted-model and language evidence required for this design.
</load_first>
Key failure modes:
- Documentation masquerades as enforcement.
- The spec patches listed instances but preserves their shared root cause.
- A broad redesign replaces the smallest boundary that could enforce the invariant.
- Different root causes are conflated into one structural change.
WHEN the input is finding-report@2, THE SYSTEM SHALL inspect every confirmed finding and supplied defect family before choosing structural boundaries.
WHEN the input is implementation-review@2, THE SYSTEM SHALL inspect every family whose disposition is architecture_escalation and preserve its instance, semantic-model, and architecture evidence.
WHEN the input is implementation-result@1, THE SYSTEM SHALL ground its architecture escalation in live code and the persisted architecture before drafting a structural correction.
WHEN the input provides workspace or requirement lineage, THE SYSTEM SHALL use the workspace for live inspection and carry linked_requirement into each resulting spec.
WHEN drafting a spec, THE SYSTEM SHALL name the defect class in purpose, the enforcing boundary in scope, and instance patches in non_goals unless migration requires them.
WHEN defining acceptance criteria, THE SYSTEM SHALL name the compile, test, lint, or CI check that fails if the invariant is violated.
IF the input contains multiple root causes spanning different subsystems, THE SYSTEM SHALL produce a separate spec for each structural boundary rather than a single spec that conflates them.
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 Changed · +1 lines 50b23ef56d22
- 1mo ago Changed · -7 lines · -168 tokens per session b93fccd8edfa
- 1mo ago Changed · +29 tokens per session 5a251982136e
- 1mo ago First seen · 57 lines · 195 tokens per session scan A 06c59ad04eb8
architect is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 19d ago), licensed MIT. It adds 56 tokens to every session and 831 once invoked, about $0.0002 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-31.
Other agents, from other repositories
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
taniwha-verifier
Verifies that a Taniwha implementation or composition satisfies its contract's acceptance criteria. Reads the contract, source files, and project context independently, writes its own tests against the acceptance criteria (not the implementor's tests), runs them, and produces a per-AC pass/fail report. Invoked by the…
evidence-collector
Independent verification agent. Takes FINAL-PLAN.md and independently verifies every acceptance criterion was met. No access to executor output.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
sdd-reviewer
Specialized SDD Subagent for Phase 4 (Quality Signoff). Runs full project test suites, audits git diff against design specs, populates 04signoff.md, and presents final quality assurance logs.