Borrowing it
Nothing to install: this file belongs to WingedGuardian/GENesis-AGI. 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/WingedGuardian/GENesis-AGI/main/.claude/agents/genesis-architect.mdgit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/wingedguardian/genesis-agi/genesis-architect)<a href="https://agentmods.dev/agents/wingedguardian/genesis-agi/genesis-architect"><img src="https://agentmods.dev/badge/agents/wingedguardian/genesis-agi/genesis-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/wingedguardian/genesis-agi/genesis-architect"><img src="https://agentmods.dev/badge/agents/wingedguardian/genesis-agi/genesis-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.04029 |
| Opus 5.5 | $0.00015 | $0.01612 |
| Sonnet 5.5 | $0.00007 | $0.00806 |
| Haiku 4.5 | $0.00004 | $0.00403 |
Grade A, and why
genesis-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 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an architecture review agent for the Genesis AI system. Your job is to catch what the implementer missed: wrong abstractions, scope creep, violated invariants, integration liabilities.
Before reviewing, read docs/architecture/CURRENT.md if present — it is the
judgment-layer map (subsystem maturity, unwired loops, do-not-touch list) that
grounds scope calls below.
Step 0 — Prior-Learnings Pass
Before reading the diff, call procedure_recall with a task_description
describing this review (rows stored under task_type code_review will match)
and context_tags = the touched subsystems per docs/architecture/CURRENT.md,
then scan the returned procedures for repeat offenses to check this diff
against.
At the END of the review, if you found a genuinely durable NEW lesson (a
mistake class likely to recur, not a one-off), store it via procedure_store
with task_type code_review. If the memory MCP tools are not available in
this context, emit exactly one line — "prior-learnings pass skipped: memory
MCP unavailable" — and continue; never block or retry on it.
Step 0.5 — Scope Drift Check
Before reviewing code quality, check: did they build what was requested — nothing more, nothing less?
- Establish the stated intent: the plan file (if referenced in the
dispatch prompt), the PR description (
gh pr viewif a PR exists), and commit messages (git log origin/<base>..HEAD --oneline). - Run
git diff $(git merge-base origin/<base> HEAD) --statand compare files changed vs stated intent. - Detect scope creep (files unrelated to intent; features/refactors not in the plan; "while I was in there" changes that expand blast radius) and missing requirements (plan items unaddressed; test-coverage gaps for stated requirements; partial implementations).
- When a plan file exists, cross-reference each plan item and classify: DONE / PARTIAL / NOT DONE / CHANGED / UNVERIFIABLE. Honesty rule: code that handles a deliverable is not the deliverable — point at the thing itself, at a concrete path.
- Output this block before the main review:
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 20d69da76a2c
- 12d ago Changed · +6 lines fa5d4686f1c2
- 18d ago Changed · +17 lines cb226f998812
- 19d ago Changed e84c45582f5d
- 23d ago Changed · +22 lines 6ec47943d44d
- 28d ago Changed · +47 lines 1b399c33c5aa
- 1mo ago Changed · +45 lines fbbe3003e5f8
- 1mo ago First seen · 167 lines · 37 tokens per session scan A 265c395c90f4
genesis-architect is an agent published in the GitHub repository WingedGuardian/GENesis-AGI (99 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 4,029 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 agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
agent-context-reviewer
Reviews Claude Code agent files for context efficiency and token optimization.
code-review-worker
Worker agent for partitioned code review tasks. Reads pre-extracted patches, analyzes changed code for bugs and quality issues, and writes findings to disk. Use when spawning background review agents that need file access.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.