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 Plazmodium/odin-workflow --skill code-review-and-qualitygit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/code-review-and-quality)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/code-review-and-quality"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/code-review-and-quality.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.00023 | $0.00321 |
| Opus 5 | $0.00012 | $0.00161 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
code-review-and-quality 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.
What it actually says
code-review-and-quality
When To Use
- Reviewing a diff or pre-merge change.
- Asked for a review.
- A change is complete enough to evaluate.
Workflow
- Determine the intended behavior and changed files.
- Review for correctness and edge cases.
- Review for safety: security, data loss, concurrency, migrations, and trust boundaries.
- Review for maintainability: clarity, names, scope, complexity, and local conventions.
- Review tests and verification evidence.
- Review change size; recommend splitting large or unrelated diffs.
- Report findings first, ordered by severity with file/line references.
- Use severity labels: Critical, Major, Minor, Nit, Optional, FYI.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "Tests pass, ship it." | Passing tests are evidence, not a review. |
| "The diff is too large to inspect closely." | Large diffs should be split, not rubber-stamped. |
| "This is only a nit." | Label nits as nits so real blockers stay visible. |
Verification
- Findings cite concrete code locations.
- No speculation is presented as fact.
- Missing tests or verification gaps are explicit.
Exit Criteria
- A human can decide whether the change is safe to merge.
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 · 44 lines · 23 tokens per session scan A 8b8913652f4c
code-review-and-quality is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 321 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-09-01.
Other skills, from other repositories
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
github-pr-sentinel
Monitor a GitHub pull request until it's merged, green, or blocked. Polls CI checks, review comments, and mergeability state continuously. Use this skill when the user asks to monitor a PR, watch CI, handle review comments, sentinel a PR, babysit a PR, or keep an eye on failures and feedback — even if they just say…
tool-description-check
Self-check a new or edited MCP tool description/field .describe() text before committing — verify every behavioral claim against live testing or source, check for contradictions with sibling tools, and score against Glama's Tool Definition Quality Score (TDQS) rubric. Use whenever a tool description or schema field…
coding-reference
Quick-reference coding standards and backend patterns for consistent development.
orch-panel
Invoke a Panel of Experts review on any artifact — code, architecture, plans, repos, or documentation.
orch-review
Trigger code review workflow with risk detection and reviewer routing.