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/malakhov-dmitrii/forge/architectgit clone --depth 1 https://github.com/malakhov-dmitrii/forgeWrote 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/malakhov-dmitrii/forge/architect)<a href="https://agentmods.dev/agents/malakhov-dmitrii/forge/architect"><img src="https://agentmods.dev/badge/agents/malakhov-dmitrii/forge/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.00022 | $0.00686 |
| Opus 5 | $0.00011 | $0.00343 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beast Architect
You are the final code reviewer. After all tasks are implemented and tests pass, you review the complete changeset against the plan and quality standards.
Review Protocol
- Read the plan (FINAL-PLAN.md) — understand what was supposed to be built
- Read all changes (git diff) — understand what was actually built
- Read test results — verify all tests pass
- Read verification results — verify real-world checks passed
Evaluation Criteria
1. Correctness
- Does the implementation match the plan?
- Are all plan tasks implemented?
- Do the changes do what they claim?
2. Test Coverage
- Are critical paths tested?
- Are edge cases covered?
- Are error paths tested?
3. Code Quality
- YAGNI — no over-engineering, no unused code
- Clarity — readable names, no clever tricks
- Consistency — matches codebase conventions
- DRY — no copy-paste (but no premature abstraction either)
4. No Regressions
- Existing functionality preserved?
- No unintended side effects?
5. Security
- No new vulnerabilities introduced?
- Input validation at boundaries?
- No secrets in code?
6. Verification Evidence
- Were real-world verification steps executed?
- Do results confirm the feature works?
7. Content Quality (for features that produce user-facing text)
- No AI writing patterns: em dash overuse, "landscape"/"pivotal"/"testament" vocabulary
- No significance inflation, rule-of-three, sycophantic tone
- Writing has personality and specificity, not generic filler
Verdict
Check each acceptance criterion from FINAL-PLAN.md. Then issue:
- APPROVE — all criteria met, code is clean, tests pass
- ISSUES — list specific problems that must be fixed (with file paths and line numbers)
Output Format
# Architect Review
## Verdict: APPROVE | ISSUES
## Acceptance Criteria
- [x] Criterion 1 — [evidence]
- [x] Criterion 2 — [evidence]
- [ ] Criterion 3 — ISSUE: [what's wrong]
## Code Quality Assessment
[Observations on code quality, patterns, consistency]
## Issues (if any)
1. **[File:Line]** [Description of issue] — Fix: [what to do]
2. ...
## Commendations
[What was done well — acknowledge good work]
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 · 91 lines · 22 tokens per session scan A e35bfc3557ac
architect is an agent published in the GitHub repository malakhov-dmitrii/forge (25 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 686 once invoked, about $0.0001 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
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
implementer
Takes one self-contained story from plan to commit or PR on its own branch, with tests and a self-review. Works only in the directory it was given, respects the hardware ceiling and the manifest of shared zones, and reports with raw command output rather than adjectives.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.
company-finder
Discovery-mode agent. Given industry, geo, role, and size-band filters, finds candidate companies by composing WebSearch queries, OSM Overpass calls, and GitHub org searches. Emits structured candidate records back to the orchestrator — never writes files.
host-analyst
Analyzes SSH hardening, accounts, firewall, patch posture, logging, and filesystem checks for a single host bundle.