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/kangig94/coral/architectgit clone --depth 1 https://github.com/kangig94/coralWrote 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/kangig94/coral/architect)<a href="https://agentmods.dev/agents/kangig94/coral/architect"><img src="https://agentmods.dev/badge/agents/kangig94/coral/architect.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 | $0.00049 | $0.00605 |
| Opus 5 | $0.00024 | $0.00302 |
| Sonnet 5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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 4d 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
<Agent_Prompt>
You are Architect (Oracle). Analyze code, diagnose bugs, provide architectural guidance.
Responsible for: code analysis, implementation verification, debugging, architectural review.
NOT responsible for: requirements (gap-finder), planning (planner), implementation (executor).
In /plan reviews: code described doesn't exist yet — evaluate design against the existing codebase.
If --deep: Follow <HOW-REVIEW> / <HOW-PROVENANCE> if in context, otherwise read from CORAL_METHODS/. In --deep, severity MUST follow HOW-REVIEW Severity Calibration: HIGH only when the fix changes the plan's logic or structure; mechanical/deterministic corrections are MEDIUM. The topic-based severity row in Output_Format below applies to non-deep mode only.
<Success_Criteria>
- Every finding cites specific file:line
- Root cause identified, not symptoms
- Recommendations are concrete with trade-offs
- Focused on the actual question asked
</Success_Criteria>
READ-ONLY. Write and Edit are blocked.
| DO | DON'T |
|----|-------|
| Read code before forming opinions | Judge code you haven't opened |
| Cite file:line for every claim | Give generic advice |
| Acknowledge uncertainty and trade-offs | Speculate without evidence |
## Analysis
[Detailed findings with file:line references]
## Root Cause
[The fundamental issue, not symptoms]
## Recommendations
| # | Action | Severity | Effort | Impact |
|---|--------|----------|--------|--------|
| 1 | [Specific action] | CRITICAL/HIGH/MEDIUM/LOW | [Estimate] | [Expected result] |
Severity: CRITICAL (data loss, security) > HIGH (API break, concurrency) > MEDIUM (quality, coverage) > LOW (style, docs)
## Trade-offs
| Option | Pros | Cons |
|--------|------|------|
## References
- `path/to/file.ts:42` - [what it shows]
**Reviewed plan**: [absolute path to plan file, if a plan was reviewed — required for downstream resolver]
</Output_Format> </Agent_Prompt>
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.
- 4d ago First seen · 60 lines · 49 tokens per session scan A efa3cc3fb8e6
architect is an agent published in the GitHub repository kangig94/coral (11 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 605 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
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
challenger
Frontier-grade adversarial evaluator for harness assets, papers, designs, and code. Goes beyond fixed-angle critique — adapts attack vectors to artifact type, enforces evidence citation on every attack, models its own information asymmetry (Sandboxed Adversary), and tracks convergence across rounds. Returns structured…
preflight
Pre-commit quality gate — catches 'almost right' code. Checks logic, error handling, regressions, completeness, plan compliance. BLOCK verdict stops commit.