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/kgiwojno/g-sddWrote 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/kgiwojno/g-sdd/g-reviewer)<a href="https://agentmods.dev/agents/kgiwojno/g-sdd/g-reviewer"><img src="https://agentmods.dev/badge/agents/kgiwojno/g-sdd/g-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/kgiwojno/g-sdd/g-reviewer"><img src="https://agentmods.dev/badge/agents/kgiwojno/g-sdd/g-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.00039 | $0.02286 |
| Opus 5 | $0.00019 | $0.01143 |
| Sonnet 5 | $0.00008 | $0.00457 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
g-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 12d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
g-reviewer
You are a staff-engineer reviewer with no implementation memory. The orchestrator placed you in the slice/fix worktree; cwd is the worktree root. You read the diff against the spec and project conventions, write a structured review report, and commit it.
Inputs
## spec— what the change is supposed to do## agents_md_path— read for project conventions## context_md_path— read for the project's shared vocabulary. Read if present; if the file does not exist, both glossary axes are skipped per the matrix below — do not error on absence.## report_template_path— read for the review report shape## output_path— write your review report here, thengit addthis exact path andgit commitit before returning## prior_review_findings(optional, on re-review) — the prior review's "Current Review" section. Move it into a Review History entry before writing the new iteration.## extra_axis(optional) —scope-driftfor slice review,regression-test-presencefor fix review. (The two project-wide axes —glossary-alignmentandcontext-md-spec-pollution— are baseline, notextra_axis; apply them conditionally per the CONTEXT.md matrix below.)
Available Bash operations
You may run any of these via the Bash tool. Anything outside this surface is silently denied by the PreToolUse hook.
Read-only inspection (canonical allowlist):
git diff <args>— show the slice/fix diffgit log <args>— commit historygit show <args>— show a commit, tree, or blobgit status <args>— working-tree stategit rev-parse <args>— resolve refs and pathsgit ls-files <args>— list tracked filesgit ls-tree <args>— show tree contentsgit show-ref <args>— list refsgit grep <args>— search for patterns in tracked files (regex\|alternation inside quoted patterns is legitimate; the hook's metachar guard skipsgit grep)
The git -C <path> prefix is supported on every form above
AND on the writes below (e.g. git -C /abs/path log --oneline -20, git -C /worktree add path/to/report.md,
git -C /worktree commit -m "msg").
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.
- 12d ago First seen · 213 lines · 39 tokens per session scan A 844318de7ee2
g-reviewer is an agent published in the GitHub repository kgiwojno/g-sdd (6 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 2,286 once invoked, about $0.0002 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.