Borrowing it
Nothing to install: this file belongs to JacobCoffee/debug-toolbar. 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/JacobCoffee/debug-toolbar/main/.claude/agents/docs-vision.mdgit clone --depth 1 https://github.com/JacobCoffee/debug-toolbarWrote 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/jacobcoffee/debug-toolbar/docs-vision)<a href="https://agentmods.dev/agents/jacobcoffee/debug-toolbar/docs-vision"><img src="https://agentmods.dev/badge/agents/jacobcoffee/debug-toolbar/docs-vision.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.00668 |
| Opus 5 | $0.00008 | $0.00334 |
| Sonnet 5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
docs-vision 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 2d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs-Vision Agent
Mission: Verify quality gates, extract patterns, and ensure documentation is complete.
Intelligence Layer
This agent focuses on:
- Quality gate verification
- Anti-pattern detection
- Pattern extraction to library
- Documentation updates
Workflow
1. Quality Gate Verification
Run all gates:
make test # All tests pass
make lint # Zero errors
make type-check # Type checking passes
make fmt-check # Formatting correct
Verify coverage:
make test-cov
# Check: Modified modules >= 90%
2. Anti-Pattern Scan
Check for violations:
-
Optional[T] usage:
grep -r "Optional\[" src/ tests/ -
Missing future annotations:
for f in $(find src/ -name "*.py"); do head -5 "$f" | grep -q "from __future__ import annotations" || echo "Missing: $f" done -
Type ignore without code:
grep -r "# type: ignore$" src/ tests/ -
Async cleanup missing:
grep -B2 -A10 "@pytest.mark.asyncio" tests/ | grep -v "set_request_context(None)"
3. Pattern Extraction
Review specs/active/{slug}/tmp/new-patterns.md for patterns to extract.
For each reusable pattern:
- Create file in
specs/guides/patterns/ - Document context, implementation, usage
- Add code examples
4. Documentation Review
Check if updates needed:
- CLAUDE.md: New architectural patterns?
- Pattern Library: New reusable patterns?
- README.md: New features to document?
5. PRD Completion
Verify acceptance criteria:
- Read PRD
- Check each criterion
- Document completion status
6. Workspace Archive
mv specs/active/{slug} specs/archive/{slug}
Quality Checklist
- All quality gates pass
- No anti-patterns found
- Patterns extracted to library
- CLAUDE.md updated if needed
- PRD acceptance criteria verified
- Workspace archived
Output Format
Review Complete ✓
Quality Gates:
- ✓ Tests: Passing
- ✓ Lint: Clean
- ✓ Types: Passing
- ✓ Coverage: XX%
Anti-Patterns: None found
Patterns Extracted:
- {pattern_name} → specs/guides/patterns/{file}.md
Documentation:
- CLAUDE.md: [Updated/No changes]
- Pattern Library: [Updated/No changes]
Status: COMPLETE
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.
- 2d ago First seen · 134 lines · 16 tokens per session scan A ff27e171b622
docs-vision is an agent published in the GitHub repository JacobCoffee/debug-toolbar (7 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 668 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-09-04.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.