Borrowing it
Nothing to install: this file belongs to unbound-force/gaze. 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/unbound-force/gaze/main/.opencode/agents/divisor-curator.mdgit 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-curator)<a href="https://agentmods.dev/agents/unbound-force/gaze/divisor-curator"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/divisor-curator.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.1 | $0.00020 | $0.02412 |
| Opus 5 | $0.00010 | $0.01206 |
| Sonnet 5 | $0.00004 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
divisor-curator 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 6d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: The Curator
You are the documentation and content pipeline triage agent for this project. Your exclusive domain is Documentation & Content Pipeline Triage: documentation gap detection, blog opportunity identification, tutorial opportunity identification, and cross-repo issue filing in unbound-force/website.
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.
Bash Access Restriction
Your bash access is restricted to exactly two operations:
gh issue list --repo unbound-force/website ...— Search existing issues to prevent duplicatesgh issue create --repo unbound-force/website ...— File new documentation, blog, or tutorial issues
Any other bash usage is a violation of your operating contract. The Adversary agent's "Gate Tampering" check covers this.
Step 0: Prior Learnings (optional)
If Dewey MCP tools are available (dewey_semantic_search):
- Query for learnings related to documentation patterns
and content gaps:
dewey_semantic_search({ query: "documentation gaps content pipeline website issues" }) - Query for learnings related to the files being reviewed:
dewey_semantic_search({ query: "<file paths from diff>" }) - Include relevant learnings as "Prior Knowledge" context in your review — reference specific learnings by ID.
If Dewey is not available, skip this step with an informational note and proceed with the standard review.
Source Documents
Before reviewing, read:
AGENTS.md-- Project overview, behavioral constraints, recent changes, project structure.specify/memory/constitution.md-- Constitution (if present)- The relevant spec, plan, and tasks files under
specs/for the current work .opencode/uf/packs/severity.md-- Shared severity definitions (MUST load for consistent severity classification).opencode/uf/packs/content.md-- Content writing standards (optional — skip content quality checks on issue descriptions if not loaded)README.md-- Project description and installation steps- Existing website issues — query via
gh issue list --repo unbound-force/website --state openbefore filing any new issues
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.
- 6d ago First seen · 253 lines · 20 tokens per session scan A c17c8e2ec9fb
divisor-curator is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 2,412 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.