Borrowing it
Nothing to install: this file belongs to projectbluefin/dakota. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/projectbluefin/dakota/testing/.agents/skills/dakota-review/SKILL.mdgit clone --depth 1 https://github.com/projectbluefin/dakotaWrote 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/projectbluefin/dakota/dakota-review)<a href="https://agentmods.dev/skills/projectbluefin/dakota/dakota-review"><img src="https://agentmods.dev/badge/skills/projectbluefin/dakota/dakota-review/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/projectbluefin/dakota/dakota-review"><img src="https://agentmods.dev/badge/skills/projectbluefin/dakota/dakota-review.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.00024 | $0.00875 |
| Opus 5 | $0.00012 | $0.00438 |
| Sonnet 5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
dakota-review 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dakota Review and Issue Workflow
Review pull requests and issues with high discipline: minimal diff, correct target branch, evidence-based verification, and strict boundaries.
When to Use
- Performing code or architecture reviews on PRs in
projectbluefin/dakota - Triaging issues, user-donated diagnostic gists (
ujust report), or verification comments - Enforcing contributor guidelines, PR checklists, and commit hygiene
When NOT to Use
- Writing code changes or authoring elements → load
dakota-buildstreamordakota-packaging - Modifying release promotion or signing gates → load
dakota-release - Authoring CI workflows → load
dakota-ci
Core Process
- Verify Target Branch: Ensure PR targets
testing(ornextif explicitly tracking rolling), nevermain. - Review Hygiene & Commits:
- Check commit format:
<type>(<scope>): <description>. - Ensure commits use
Assisted-by:, neverCo-authored-by:.
- Check commit format:
- Inspect Implementation:
- Ensure image changes use BuildStream elements (no DNF, RPMs, or Containerfiles).
- Ensure layer additions use
kind: compose(neverkind: stack). - Check that third-party GitHub Actions are pinned to full commit SHAs.
- Evaluate Evidence:
- For bugs, check for attached gists from
ujust report. - Verify that claimed test results were actually executed (
just validate,just boot-test, etc.).
- For bugs, check for attached gists from
- Constructive Feedback:
- If asked to post feedback, compose at most one concise, actionable comment.
- Never restate GitHub UI status (e.g. "checks are passing").
Invariants
- PROHIBITION ON
ublue-os/*: Never write to anyublue-os/*repository under any circumstance. Ask a human to report upstream manually. - Commit Trailer Invariant: Use
Assisted-by:, neverCo-authored-by:. - Target Branch: PRs must target
testing.mainis a release bookmark. - Hardware Evidence Priority:
verified: N/3on issues is post-ship proof that cannot be substituted by CI. Do not close bugs without hardware verification or explicit maintainer direction. - Communication Etiquette: Do not post automated comments or review messages unless explicitly commanded by the user.
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.
- 2d ago Changed · +19 lines d90e2a14ad24
- 11d ago First seen · 58 lines · 24 tokens per session scan A 46b1f603831b
dakota-review is a skill published in the GitHub repository projectbluefin/dakota (151 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 875 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
kicad-pcb-review
Use this skill when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.
arch-review
Read-only architecture review of RTL vs uArch spec with area/timing/power tradeoffs. Use for post-RTL architecture sign-off or suspected spec mismatch.
cdc-tool-profiles
Internal reference: cdc tool profiles (agent-loaded; do not invoke).
rtl-review
Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.
kicad-pcb-review
KiCad PCB review and manufacturing readiness agent skill for Cursor.
code-review-policy
Internal reference: code review policy (agent-loaded; do not invoke).