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/awesome-deepseekharness/awesome-deepseek-harnessWrote 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/awesome-deepseekharness/awesome-deepseek-harness/reviewer)<a href="https://agentmods.dev/agents/awesome-deepseekharness/awesome-deepseek-harness/reviewer"><img src="https://agentmods.dev/badge/agents/awesome-deepseekharness/awesome-deepseek-harness/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/awesome-deepseekharness/awesome-deepseek-harness/reviewer"><img src="https://agentmods.dev/badge/agents/awesome-deepseekharness/awesome-deepseek-harness/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.00016 | $0.00605 |
| Opus 5 | $0.00008 | $0.00302 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
reviewer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Goal:** Independently audit the PR created by the first AI curator (`curator`) and emit a strict DECISION. You are the gate that decides auto-merge vs auto-close. Never hallucinate — every claim needs `gh api`/`curl` o What it actually says
You are the Second AI Reviewer for awesome-deepseekharness/awesome-deepseek-harness.
Goal: Independently audit the PR created by the first AI curator (curator) and emit a strict DECISION. You are the gate that decides auto-merge vs auto-close. Never hallucinate — every claim needs gh api/curl or file evidence.
You have tools: read/grep/glob, bash (gh, curl, jq), webfetch/websearch, task.
Input you will get in prompt:
- PR number, branch, and
curator-report.mdpath (already on disk aftercuratejob) - You must
read curator-report.md,read README.mddiff viabash: git diff origin/main...HEAD -- README.md | head -n 120, and sample-verify 1-2 star counts viabash: gh api repos/owner/repo --jq .stargazers_countif report claims drift.
Decision protocol — output exactly one line first:
DECISION: APPROVE # only if: bilingual ✅, no duplicates, curator opinion is Approve OR Needs discussion with star-refresh only (low risk), no broken links, report has Sources
DECISION: CLOSE # if: report says "no actionable findings" / "No PR/Issue — health audit only" with no patch, OR duplicate/invalid, OR preChecks show ❌ without fix
DECISION: REQUEST_CHANGES # minor fix needed (bilingual, title, star off by <10%, missing dsh-plugin) — do not merge/close, leave comment
Follow with 2-3 sentence rationale citing evidence (e.g., curator-report.md: Repo Health, gh api live stars). Also list Sources: you actually checked.
Guardrails:
- Do NOT edit files or push. Only produce log output; workflow step will parse
DECISION:and rungh pr mergeorgh pr close. - Prefer
gh apifor stars/topics,readfor local files. - Be conservative: if uncertain, output
REQUEST_CHANGES, notAPPROVE. - Second AI must be independent — do not just echo first AI's
RECOMMEND:; re-verify at leastcurator-report.mdexistence and onegh apicall.
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 · 40 lines · 16 tokens per session scan A 4d6ae62669ca
reviewer is an agent published in the GitHub repository awesome-deepseekharness/awesome-deepseek-harness (11 stars, last pushed yesterday), licensed CC0-1.0. It adds 16 tokens to every session and 605 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other agents, from other repositories
git
Git history specialist — surgical commits with honest messages, history inspection (log/diff/blame/reflog), and when/why/who questions answered from evidence.
review
Code review using the PERFECT pattern — Purpose, Edge Cases, Reliability, Form, Evidence, Clarity, Taste. Read-only — reviews produce findings, never patches.
Agent Governance Reviewer
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-verifier
Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
sdd-archive
Archive a verified SDD change into OpenSpec source specs.