triangulated-code-review

triangulated-code-review is a skill for Claude Code from donnfelker/loop-skills. It costs 163 tokens per session (7,272 once invoked), scanned A, original, MIT.

A code-review workflow that runs several specialised reviews in parallel, then has a separate reviewer check the reported findings. It produces one prioritised report saved to disk.

In plain words
What is it for?
Use it for broad code reviews covering correctness, security, adversarial concerns, and claims that need verification.
Why use it?
It reduces the chance that a single reviewer misses a defect or reports an unsupported claim, especially about third-party libraries.

Skill for Claude Code

Written for Claude Code: $CLAUDE_PLUGIN_ROOT variable. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/foo/code/myrepo.

Part of the triangulated-code-review plugin — 1 skill shipped together

Good fit Use it for broad code reviews covering correctness, security, adversarial concerns, and claims that need verification.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add donnfelker/loop-skills
Claude Code
/plugin install triangulated-code-review

Made for: Claude Code.

Or install triangulated-code-review, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for triangulated-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/donnfelker/loop-skills/triangulated-code-review.svg)](https://agentmods.dev/skills/donnfelker/loop-skills/triangulated-code-review)
Your own site
<a href="https://agentmods.dev/skills/donnfelker/loop-skills/triangulated-code-review"><img src="https://agentmods.dev/badge/skills/donnfelker/loop-skills/triangulated-code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 163 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,272 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00163 $0.07272
Opus 5 $0.00081 $0.03636
Sonnet 5 $0.00033 $0.01454
Haiku 4.5 $0.00016 $0.00727

Measured 8d ago against content hash a77924522e06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

triangulated-code-review scanned grade A with 1 finding 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 8d 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.

Reads agent configuration directorieslowAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- `<SKILL_DIR>` → absolute path of this skill's directory. Resolve this from the orchestrator's runtime: it is the directory containing the SKILL.md you are reading. If unsure, run `find ~/.claude/plugins -path '*triangu

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

plugins/triangulated-code-review/skills/triangulated-code-review/SKILL.md · 397 lines

How it starts

The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Triangulated Code Review Orchestrator

You are the review lead. Your job is to coordinate up to four specialized reviewers in parallel, triangulate their findings into one prioritized report, and save that report to disk so the user (and future-you) can refer back to it.

Announce at start: "I'm using the triangulated-code-review orchestrator skill — let me confirm which reviewers to run."

Why this skill exists

Single-reviewer passes miss things. This skill borrows from research methodology: triangulating a finding against multiple independent sources reduces blind spots. A comprehensive reviewer catches correctness defects; a security reviewer catches OWASP-style vulns; Codex catches things a single model often doesn't; an adversarial Codex pass questions whether the chosen approach is even right. Running them in parallel and merging gets you broader coverage in roughly the wall-clock time of the slowest reviewer.

But broader coverage means more chances for a confident-but-wrong claim to slip through — particularly around third-party library APIs, where reviewers regularly hallucinate function signatures or deprecation status. A final QA analyst pass substantiates every finding before it's locked into the report: it re-checks the cited file/line, walks the reasoning, and for any claim that touches an external library, verifies actual current usage via the context7 MCP. Findings the QA analyst can't substantiate are demoted into a dedicated section of the report rather than silently dropped — the user still gets to see what was flagged and why it was rejected.

The merged + QA-validated report is saved to a timestamped file so you can re-run later and diff against the previous report to see what changed.

Process flow

1. Sanity-check git state
2. Ask which reviewers to run (AskUserQuestion, multi-select)
3. Spawn one subagent per selected reviewer — in parallel, single message
4. Wait for ALL subagents (no partial synthesis)
5. Merge + prioritize findings (conservative dedupe) into a draft
6. Spawn QA analyst subagent to substantiate every draft finding
   (uses context7 MCP for any third-party library claims)
7. Apply QA verdicts — move invalidated findings to their own section
8. Write timestamped report to CWD
9. Tell the user where the file is and present top findings

Read the full file on GitHub · 397 lines

Files

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.

Changes

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.

  1. 8d ago First seen · 397 lines · 163 tokens per session scan A a77924522e06

Subscribe to this mod's changes

triangulated-code-review is a skill published in the GitHub repository donnfelker/loop-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 163 tokens to every session and 7,272 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.