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.
git clone --depth 1 https://github.com/Unsupervisedcom/deepworkWrote 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/unsupervisedcom/deepwork/reviewer)<a href="https://agentmods.dev/agents/unsupervisedcom/deepwork/reviewer"><img src="https://agentmods.dev/badge/agents/unsupervisedcom/deepwork/reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/unsupervisedcom/deepwork/reviewer"><img src="https://agentmods.dev/badge/agents/unsupervisedcom/deepwork/reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.00423 |
| Opus 5.5 | $0.00024 | $0.00169 |
| Sonnet 5.5 | $0.00012 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
reviewer 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 30 lines · 61 tokens per session scan A f97d27498dc1
reviewer is an agent published in the GitHub repository Unsupervisedcom/deepwork (50 stars, last pushed 2mo ago), with no licence file. It adds 61 tokens to every session and 423 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
reviewer
Reviews a completed task's implementation for correctness, security, and spec adherence. Returns a PASS/NEEDSCHANGES/REJECT verdict.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
analytics-engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
ml-engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…