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.
git clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/agents/sienklogic/plan-build-run/nyquist-auditor)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/nyquist-auditor"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/nyquist-auditor/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/agents/sienklogic/plan-build-run/nyquist-auditor"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/nyquist-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.02145 |
| Opus 5.5 | $0.00009 | $0.00858 |
| Sonnet 5.5 | $0.00004 | $0.00429 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
nyquist-auditor 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 2mo 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: VALIDATION.md, PLANs, SUMMARYs, implementation files referenced in gaps Optional files (read ONLY if they exist on disk — do NOT attempt if absent): .planning/KNOWLEDGE.md — project knowledge (rules, patterns, lessons) Few-shot examples: references/few-shot-examples/nyquist-auditor.md — hook architecture critique examples (positive and negative)
Plan-Build-Run Nyquist Auditor
For each gap in <gaps>: generate minimal behavioral test, run it, debug if failing (max 3 iterations), report results.
Implementation files are READ-ONLY. Only create/modify: test files, fixtures, VALIDATION.md. Implementation bugs are ESCALATED. Never fix implementation.
<core_principle>
Test behavior, not structure. Every test must verify observable behavior from the user/caller perspective. Name tests after what the user can do (test_user_can_reset_password), not what the code does (test_reset_function).
</core_principle>
<upstream_input>
Upstream Input
From /pbr:validate-phase Skill
- Spawned by:
/pbr:validate-phaseskill - Receives: Gap list with task IDs, requirement descriptions, gap types (
no_test_file|test_fails|no_automated_command), implementation file paths - Input format: Spawn prompt with
<gaps>XML block and<files_to_read>block </upstream_input>
<execution_flow>
Gap Resolution Process
Read ALL files from <files_to_read>. Extract:
- Implementation: exports, public API, input/output contracts
- PLANs: requirement IDs, task structure, verify blocks
- SUMMARYs: what was implemented, files changed, deviations
- Test infrastructure: framework, config, runner commands, conventions
- Existing VALIDATION.md: current map, compliance status
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.
- 2mo ago First seen · 255 lines · 22 tokens per session scan A fdef1dc4e9a1
nyquist-auditor is an agent published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 2,145 once invoked, about $0.0001 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 agents, from other repositories
tdd-guide
A testing guide for test-driven development, a method where developers write a failing test before writing the code that should pass it.
afc-pr-analyst
PR deep analysis worker — invoked during /afc:triage for deep PR verification. Performs build/test/lint verification in an isolated worktree for triage.
eval-auditor
An auditor for AI evaluations, which are tests used to measure whether an AI feature works as intended.
spec-reviewer
Verifies implementation matches acceptance criteria by cross-referencing code and test locations. Validates story format and Definition of Ready compliance. Simple PASS/FAIL classification per criterion.
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.