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 skills add Undertone0809/rudder --skill advisor-review-loop-maintainergit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/advisor-review-loop-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/advisor-review-loop-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/advisor-review-loop-maintainer/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/skills/undertone0809/rudder/advisor-review-loop-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/advisor-review-loop-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 108 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 324 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00057 | $0.03524 |
| Opus 5.5 | $0.00023 | $0.01410 |
| Sonnet 5.5 | $0.00011 | $0.00705 |
| Haiku 4.5 | $0.00006 | $0.00352 |
Grade A, and why
advisor-review-loop-maintainer 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.
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advisor Review Loop Maintainer
This skill chains existing Rudder maintainer practices:
build-advisor: turn fuzzy dissatisfaction or a high-stakes request into a grounded scenario analysis, requirement map, options, and recommended plan.agent-work-reviewer-maintainer: independently judge whether the result solved the right product problem with sufficient behavior, evidence, and validation.product-acceptance-verifier-maintainer: when the loop evaluates delivered product behavior rather than a proposal artifact, prove black-box acceptance before final review.
Use this skill when the work should not be accepted after one author pass. The goal is to create a reviewable proposal or implementation, expose it to independent pressure, revise it, and only hand off once the remaining risk is explicit.
When to Use
Use this skill for Rudder development tasks where the user asks for any of:
- Build Advisor followed by reviewer agents
- first-principles product, scenario, or requirement analysis that must pass independent reviewers, repeated review rounds, or an explicit acceptance gate
- deep corner-case coverage before implementation or handoff
- two review iterations before the final answer
- "no pass, keep reworking" behavior
- review of a plan, skill, workflow, feature, UI, architecture, release verification, or completed agent task where correctness depends on product judgment and an acceptance gate
Do not use this skill for a narrow bug fix, simple command, ordinary code review, direct release execution, or a generic first-principles advisory task where the correct specialized skill can execute directly.
If the user explicitly names this skill for a narrow screenshot-driven UI fix but does not ask for reviewer agents, repeated rounds, "no pass then rework", or an acceptance gate, use the lightweight route:
- Do a short advisor check to confirm the UI problem and non-goals.
- Hand the implementation to
rudder-ui-polish-maintainerdiscipline. - Report that this was a lightweight advisor route, not a full reviewer loop.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 381 lines · 57 tokens per session scan A 9525363c15a0
advisor-review-loop-maintainer is a skill published in the GitHub repository Undertone0809/rudder (294 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 3,524 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 skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…