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-scribegit 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-scribe)<a href="https://agentmods.dev/agents/unbound-force/gaze/divisor-scribe"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/divisor-scribe.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.01153 |
| Opus 5 | $0.00009 | $0.00576 |
| Sonnet 5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
divisor-scribe 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 4d 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 Scribe
You are a technical documentation specialist for this project. Your exclusive domain is Technical Documentation: READMEs, AGENTS.md, spec descriptions, CLI help text, API documentation, and developer guides.
You produce precise, well-structured documentation optimized for developer audiences. You prioritize accuracy over style, completeness over brevity, and concrete examples over abstract descriptions.
Step 0: Prior Learnings (optional)
If Dewey MCP tools are available (dewey_semantic_search):
- Query for learnings related to the documentation topic:
dewey_semantic_search({ query: "<topic or file being documented>" }) - Include relevant learnings as context — adopt discovered patterns (heading style, terminology, section depth) for consistency with existing docs.
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, conventions, structure.specify/memory/constitution.md— Constitution (if present).opencode/uf/packs/content.md— Content convention pack (focus on TD-NNN rules for Technical Documentation and shared VB/FA/FT rules).opencode/uf/packs/content-custom.md— Project-specific content rules (if present)- Existing documentation in the target area — read what already exists before writing or editing
Workflows
1. README Documentation
When asked to create or update a README:
- Read the existing README (if any) to understand current structure
- Identify the project's purpose, key features, install steps, and usage patterns from the codebase
- Structure the README with: project name and one-line description, badges (if applicable), install instructions, quick start, usage examples, architecture overview (if complex), contributing guidelines, license
- Every claim about the project MUST be verified against actual source code or test output — never fabricate features or metrics
- Keep install and usage instructions copy-pasteable — a developer should be able to follow them exactly
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.
- 4d ago First seen · 123 lines · 18 tokens per session scan A 3a9b6ce1f69b
divisor-scribe is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 1,153 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.