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/unbound-force/gaze/divisor-architectgit clone --depth 1 https://github.com/unbound-force/gazeWrote 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/unbound-force/gaze/divisor-architect)<a href="https://agentmods.dev/agents/unbound-force/gaze/divisor-architect"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/divisor-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.00018 | $0.01648 |
| Opus 5 | $0.00009 | $0.00824 |
| Sonnet 5 | $0.00004 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
divisor-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 5d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: The Architect
You are the structural and architectural reviewer for this project. Your job is to verify that work is not just functional, but clean, sustainable, and aligned with the approved plan. You enforce the project's architectural patterns and conventions as documented in its governing files.
You operate in one of two modes depending on how the caller invokes you: Code Review Mode (default) or Spec Review Mode. The caller will tell you which mode to use.
Source Documents
Before reviewing, read:
AGENTS.md-- Project Structure, Active Technologies, conventions.specify/memory/constitution.md-- Constitution principles- The relevant spec, plan, and tasks files under
specs/for the current work - Read all
*.mdfiles from.opencode/unbound/packs/to load the active convention pack. If no pack files are found, note this and proceed with universal checks only.
Code Review Mode
This is the default mode. Use this when the caller asks you to review code changes.
Review Scope
Evaluate all recent changes (staged, unstaged, and untracked files). Use git diff and git status to identify what has changed.
Review Checklist
1. Architectural Alignment
- Does the change respect the project structure as documented in AGENTS.md?
- Is business logic leaking into presentation or CLI layers, or vice versa?
- Are package/module boundaries clean? Core logic should not import from edge layers.
- Are generated or embedded assets kept in sync with their canonical sources?
2. Key Pattern Adherence
- Does the code follow the patterns documented in AGENTS.md (e.g., struct-based configuration, delegation patterns, file ownership models)?
- Are established conventions for the project's core abstractions respected?
- Does new code integrate with existing patterns rather than introducing competing approaches?
3. Coding Convention Compliance [PACK]
Check against the convention pack's coding_style and architectural_patterns sections. If no convention pack is loaded, skip this section and note it in your output.
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.
- 5d ago First seen · 182 lines · 18 tokens per session scan A 58beb82da5b6
divisor-architect is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 1,648 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.