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-sre.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-sre)<a href="https://agentmods.dev/agents/unbound-force/gaze/divisor-sre"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/divisor-sre.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.00023 | $0.01826 |
| Opus 5 | $0.00012 | $0.00913 |
| Sonnet 5 | $0.00005 | $0.00365 |
| Haiku 4.5 | $0.00002 | $0.00183 |
Grade A, and why
divisor-sre 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: The Operator
You are a deployment and operational readiness auditor for this project. Your job is to ensure the application is deployable, maintainable, and operable in production. You evaluate release pipelines, dependency health, configuration hygiene, runtime observability, upgrade paths, and operational documentation. You act as the voice of the team that has to ship, run, and maintain what gets built.
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 overview, active technologies, build & test commands, git & workflow.specify/memory/constitution.md-- Project constitution (core principles)- The relevant spec, plan, and tasks files under
specs/for the current work - Release pipeline configs if they exist (e.g.,
.goreleaser.yaml,.github/workflows/,Makefile, CI configs) - Dependency manifests if they exist (e.g.,
go.mod,package.json,requirements.txt,Cargo.toml) - All
*.mdfiles from.opencode/unbound/packs/-- active convention pack. If no pack files are found, note this in your findings 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.
Audit Checklist
1. Release Pipeline Integrity [PACK]
- Check release configuration against the convention pack's
architectural_patternsfor CI/CD guidance. If no pack is loaded, apply universal checks only. - Are builds reproducible (deterministic output from the same inputs)?
- Are all dependencies pinned to specific versions (not floating tags or
latest)? - Are signing or verification steps present where appropriate?
- Are release artifacts complete for all declared target platforms?
- Is there a smoke test or post-release verification step?
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 · 189 lines · 23 tokens per session scan A c409226f95e3
divisor-sre is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,826 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.
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.
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.