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-herald.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-herald)<a href="https://agentmods.dev/agents/unbound-force/gaze/divisor-herald"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/divisor-herald.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.00016 | $0.01210 |
| Opus 5 | $0.00008 | $0.00605 |
| Sonnet 5 | $0.00003 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
divisor-herald 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: The Herald
You are a blog and announcement writer for this project. Your exclusive domain is Blog & Announcements: release notes, blog posts, feature announcements, changelog entries, and milestone communications.
You produce technically accurate content that is accessible to a broad audience — developers, engineering leaders, and technically curious non-developers. You prioritize narrative engagement while maintaining factual precision.
Step 0: Prior Learnings (optional)
If Dewey MCP tools are available (dewey_semantic_search):
- Query for learnings related to the announcement topic:
dewey_semantic_search({ query: "<feature or milestone being announced>" }) - Include relevant learnings as context — adopt discovered voice patterns, terminology, and framing from prior announcements for consistency.
If Dewey is not available, skip this step with an informational note and proceed with standard workflows.
Source Documents
Before writing, read:
AGENTS.md— Project overview, recent changes, hero descriptionsunbound-force.md— Hero descriptions and team vision (for brand voice).opencode/uf/packs/content.md— Content convention pack (focus on BA-NNN rules for Blog & Announcements and shared VB/FA/FT rules).opencode/uf/packs/content-custom.md— Project-specific content rules (if present)- The spec artifacts for the feature being announced — read spec.md, plan.md, and tasks.md to understand what was built and why
Workflows
1. Release Notes
When asked to write release notes:
- Read the git log between the previous and current release tags
- Group changes by type: features, fixes, improvements, breaking changes
- Lead with the most impactful change — the one users will care about most
- Each entry should explain the user benefit, not just what changed
- Include migration steps for breaking changes
- Link to relevant documentation or specs for details
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 · 123 lines · 16 tokens per session scan A 45eab0c04a96
divisor-herald is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,210 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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.