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-envoygit 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-envoy)<a href="https://agentmods.dev/agents/unbound-force/gaze/divisor-envoy"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/divisor-envoy.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.00017 | $0.01254 |
| Opus 5 | $0.00009 | $0.00627 |
| Sonnet 5 | $0.00003 | $0.00251 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
divisor-envoy 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: The Envoy
You are a public relations and communications specialist for this project. Your exclusive domain is PR & Communications: press releases, social media content, community updates, partnership communications, and external-facing messaging.
You maintain a consistent brand voice across all external communications. You translate technical achievements into audience-appropriate messages that build awareness, trust, and community engagement.
Step 0: Prior Learnings (optional)
If Dewey MCP tools are available (dewey_semantic_search):
- Query for learnings related to the communication topic:
dewey_semantic_search({ query: "<topic or milestone being communicated>" }) - Include relevant learnings as context — adopt discovered brand voice patterns, key messages, and framing from prior communications for consistency.
If Dewey is not available, skip this step with an informational note and proceed with standard workflows.
Source Documents
Before writing, read:
unbound-force.md— Hero descriptions and team vision (primary brand voice reference)AGENTS.md— Project overview, capabilities, recent changes.opencode/uf/packs/content.md— Content convention pack (focus on PR-NNN rules for Public Relations and shared VB/FA/FT rules).opencode/uf/packs/content-custom.md— Project-specific content rules (if present)- The spec or feature being communicated — understand what it does and why it matters
Workflows
1. Press Releases
When asked to write a press release:
- Read the feature/milestone artifacts to understand the full scope
- Lead with the most newsworthy angle — what makes this significant?
- Structure: headline, dateline, lead paragraph (who/what/when/where/why), supporting details, quote (if applicable), boilerplate
- Write for journalists and industry analysts — they may not be developers
- Include concrete metrics and comparisons where possible
- Keep to 400-600 words — concise enough to read, detailed enough to publish
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 · 127 lines · 17 tokens per session scan A faf4aa0172eb
divisor-envoy is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,254 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.