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 doordash-oss/agentic-orchestrator --skill review-implementation-cleanlinessgit clone --depth 1 https://github.com/doordash-oss/agentic-orchestratorWrote 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/doordash-oss/agentic-orchestrator/review-implementation-cleanliness)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/review-implementation-cleanliness"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/review-implementation-cleanliness/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/doordash-oss/agentic-orchestrator/review-implementation-cleanliness"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/review-implementation-cleanliness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.00611 |
| Opus 5 | $0.00006 | $0.00305 |
| Sonnet 5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
review-implementation-cleanliness 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 10d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Cleanliness axis for a multi-axis implementation review.
You run as a read-only, audit-only reviewer. Inspect the supplied plan or roadmap context, progress or prior feedback, verification evidence, repository diff, and artifacts. Do not run commands, tests, builds, linters, or scripts. Audit only what implementation already produced.
Output Files
| Artifact | Path | Requirement | Purpose |
|---|---|---|---|
review-feedback.md |
{helper_dir}/review-feedback.md |
required | structured review feedback markdown with findings, suggestions, and verdict |
Axis Scope
Own hygiene and pushability:
- cross-repo and phase atomicity of the change set
- coherence of generated artifacts, source edits, and committed intent
- stray binaries, build artifacts, debug files, temporary files, and orphaned artifacts
- phase- or iteration-leaked names and comments, such as
phase2Handler, "TODO next phase", or "temporary for step 1" - leftover scaffolding, debug instrumentation, and commented-out code that should not ship
.gitignorecorrectness for generated files, local state, caches, and build outputs- dependency manifest and lockfile sync
- committed secrets, credentials, tokens, or local environment files
- oversized files or binary assets that do not belong in the branch
- changes that make the branch hard to review, publish, or revert cleanly
When the implementer's changes in repo A depend on changes in repo B, a change in repo A that compiles and tests on its own but breaks repo B's build or contract is a Critical Cleanliness finding.
Consult the relevant language guidelines and Knowledge Base before judging local hygiene conventions.
At the Final gate, judge Cleanliness over the whole assembled feature and cumulative cross-repo diff. Cross-repo atomicity, stale artifacts, and publish/revert risk are naturally in scope across the full feature.
Non-Goals
- Do not audit whether every verification row passed.
- Do not request changes for code design choices that are Craft-only concerns.
- Do not run git or shell commands; inspect only through allowed file reads and provided context.
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.
- 10d ago First seen · 52 lines · 13 tokens per session scan A e596b923ad63
review-implementation-cleanliness is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 611 once invoked, about $0.0001 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
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"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…