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 skills/dgk-dev/dgk-gpt/rrrnpx skills add dgk-dev/dgk-gpt --skill rrrgit clone --depth 1 https://github.com/dgk-dev/dgk-gptWrote 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/skills/dgk-dev/dgk-gpt/rrr)<a href="https://agentmods.dev/skills/dgk-dev/dgk-gpt/rrr"><img src="https://agentmods.dev/badge/skills/dgk-dev/dgk-gpt/rrr.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.00049 | $0.00608 |
| Opus 5 | $0.00024 | $0.00304 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
rrr 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 6d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rrr
Use glm-review --model glm-5 as the deeper paid review pass, then validate the results against the code before you trust them.
Default Flow
- Determine the exact review scope first.
- commit hash known -> commit mode
staged-> staged modepr-> PR mode- mixed unrelated local changes -> focused diff file
- Run a health check only when auth or connectivity looks questionable:
glm-review --model glm-5 --health
- Run the review with the smallest correct input:
glm-review --model glm-5
glm-review --model glm-5 --mode staged
glm-review --model glm-5 --mode pr
glm-review --model glm-5 --mode commit --ref <COMMIT_HASH>
glm-review --model glm-5 --diff-file /tmp/glm-review-diff.patch
- Verify every reported issue in the actual code and diff.
- Keep only confirmed issues.
- If fixes are requested or clearly in scope, apply them and rerun the closest verification.
Choosing Review Input
- committed single change:
glm-review --model glm-5 --mode commit --ref <COMMIT_HASH>
- committed subset of files:
glm-review --model glm-5 --mode commit --ref <COMMIT_HASH> --files src/a.ts src/b.ts
- custom focused diff:
GIT_ROOT=$(git rev-parse --show-toplevel)
cd "$GIT_ROOT" && git diff HEAD -- <file1> <file2> ... > /tmp/glm-review-diff.patch
glm-review --model glm-5 --diff-file /tmp/glm-review-diff.patch
If the diff is empty, stop and say there is nothing to review.
Validation Rules
glm-reviewis a reviewer, not an oracle.- Re-check referenced code paths before reporting a bug.
- Separate confirmed defects from debatable style feedback.
- If a finding depends on broader context, inspect the relevant surrounding code before accepting it.
Error Handling
command not found: glm-reviewInstall it withnpm install -g glm-reviewZAI_API_KEY not setExportZAI_API_KEYin the shell or your normal secret-loading path- auth or API failure
Re-run
glm-review --model glm-5 --healthafter refreshing credentials
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.
- 6d ago First seen · 85 lines · 49 tokens per session scan A a33e7bf7e0db
rrr is a skill published in the GitHub repository dgk-dev/dgk-gpt (53 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 608 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-30.
Other skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by main printing-press SKILL.md (Phase 4.85) and printing-press-polish…
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
genie-orca-review
Independent, read-only review of a group, a wish, or a PR on Orca — SHIP / FIX-FIRST / BLOCKED with severity-tagged findings. Council and retro are this skill with a different input.