Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardnpx agentmods add skills/blackbelttechnology/pi-agent-dashboard/code-qualityWrote 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/blackbelttechnology/pi-agent-dashboard/code-quality)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/code-quality"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/code-quality/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/blackbelttechnology/pi-agent-dashboard/code-quality"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/code-quality.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.00077 | $0.01428 |
| Opus 5.5 | $0.00031 | $0.00571 |
| Sonnet 5.5 | $0.00015 | $0.00286 |
| Haiku 4.5 | $0.00008 | $0.00143 |
Grade A, and why
code-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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality (Biome)
Analyze → fix → test, drivable by the goal-plugin's judge loop. The skill is the HOW; the goal is the WHEN-TO-STOP (judge reads one exit code).
Pick the mode
flowchart TD
Q{Driving a goal /<br/>cleaning your own work?}
Q -->|default| C[CHANGED-FILES MODE<br/>goal loop · git diff vs develop<br/>surgical, low blast radius]
Q -->|explicit cleanup| W[WHOLE-REPO MODE<br/>human-gated · one package,<br/>one rule-group per turn]
C --> CC[npm run quality:changed]
W --> WW["biome lint <pkg> --only=<group>"]
When unsure, use changed-files mode. Never turn whole-repo autofix loose inside a goal loop.
The oracle (what the judge reads)
One command, one exit code:
npm run quality:changed
# = biome check --changed --error-on-warnings --write (safe-fix the diff)
# && node scripts/tsc7.mjs --noEmit (type gate, TypeScript 7)
# && npm test (test gate)
- exit 0 → Biome clean (warn+error) on changed files, types compile, tests green → goal achieved.
- non-zero → fix the reported issues, run again. The judge says continue.
--changed compares the committed branch state against develop (the repo's
integration branch, set as vcs.defaultBranch in biome.json). Uncommitted or
untracked files are NOT scoped by --changed — commit your work first, or pass an
explicit path.
Procedure (every turn)
1. ANALYZE
npm run quality:changed # or: biome lint . --reporter=json (whole-repo)
Read the JSON. Group issues: safe-fixable vs unsafe vs manual.
2. FIX (surgical — only files in the diff)
- Safe fixes are already applied by `--write`. Confirm they're sane.
- Type errors + unsafe-rule + manual issues: edit by hand, minimally.
- DO NOT run `--unsafe` in the loop. Surface unsafe fixes as a report.
- DO NOT touch files outside the diff (AGENTS.md surgical rule).
3. TEST (the gate)
node scripts/tsc7.mjs --noEmit && npm test
- Red? REVERT this fix batch. Never stack broken autofixes.
- Green + 0 issues on scope? Done. Else 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.
- 7d ago Changed 45244c4cc17a
- 1mo ago First seen · 127 lines · 77 tokens per session scan A ef188b2e30af
code-quality is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (325 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,428 once invoked, about $0.0003 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
goga-review-plan
Verify execution plan completeness and correctness.
goga-accept-manifest-review
Verify each Cell's CODEMANIFEST against the implementation.
goga-change-manifest-reconciler
Reconciliation of CODEMANIFEST specifications with implementation.
goga-change-validator
Final end-to-end validation of the completed change.
goga-accept-report
Generate the final acceptance report with verdict.
goga-change-drift-analyzer
Semantic drift detection after implementation.