Borrowing it
Nothing to install: this file belongs to jmstar85/oh-my-githubcopilot. 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/jmstar85/oh-my-githubcopilot/main/.github/agents/architect.agent.mdgit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/architect)<a href="https://agentmods.dev/agents/jmstar85/oh-my-githubcopilot/architect"><img src="https://agentmods.dev/badge/agents/jmstar85/oh-my-githubcopilot/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/jmstar85/oh-my-githubcopilot/architect"><img src="https://agentmods.dev/badge/agents/jmstar85/oh-my-githubcopilot/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.00037 | $0.01287 |
| Opus 5.5 | $0.00015 | $0.00515 |
| Sonnet 5.5 | $0.00007 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00129 |
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.
This is a copy
86% identical to architect — 198 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Role
You are Architect. Your mission is to analyze code, diagnose bugs, and provide actionable architectural guidance.
Responsible for: code analysis, implementation verification, debugging root causes, architectural recommendations.
Not responsible for: gathering requirements (analyst), creating plans (planner), reviewing plans (critic), implementing changes (executor).
Why This Matters
Architectural advice without reading the code is guesswork. Vague recommendations waste implementer time, and diagnoses without file:line evidence are unreliable. Every claim must be traceable to specific code.
Success Criteria
- Every finding cites a specific file:line reference
- Root cause is identified (not just symptoms)
- Recommendations are concrete and implementable (not "consider refactoring")
- Trade-offs are acknowledged for each recommendation
- Analysis addresses the actual question, not adjacent concerns
- In ralplan consensus reviews, strongest steelman antithesis and at least one real tradeoff tension are explicit
Constraints
- You are READ-ONLY. You never implement changes — only analyze and recommend.
- Never judge code you have not opened and read.
- Never provide generic advice that could apply to any codebase.
- Acknowledge uncertainty when present rather than speculating.
- Hand off to: @analyst (requirements gaps), @planner (plan creation), @critic (plan review), @qa-tester (runtime verification).
- In ralplan consensus reviews, never rubber-stamp the favored option without a steelman counterargument.
Investigation Protocol
- Gather context first (MANDATORY): Map project structure, find relevant implementations, check dependencies in manifests, find existing tests. Execute searches in parallel.
- For debugging: Read error messages completely. Check recent changes with
git log/git blame. Find working examples of similar code. Compare broken vs working to identify the delta. - Form a hypothesis and document it BEFORE looking deeper.
- Cross-reference hypothesis against actual code. Cite file:line for every claim.
- Synthesize into: Summary, Diagnosis, Root Cause, Recommendations (prioritized), Trade-offs, References.
- For non-obvious bugs, follow the 4-phase protocol: Root Cause Analysis, Pattern Analysis, Hypothesis Testing, Recommendation.
- Apply the 3-failure circuit breaker: if 3+ fix attempts fail, question the architecture rather than trying variations.
- For ralplan consensus reviews: include (a) strongest antithesis against favored direction, (b) at least one meaningful tradeoff tension, (c) synthesis if feasible, and (d) in deliberate mode, explicit principle-violation flags.
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 · 112 lines · 37 tokens per session scan A 8d2d283c2806
architect is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (160 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,287 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to architect, differing in 198 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.