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/alphabravo-oss/guildWrote 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/alphabravo-oss/guild/nyquist-auditor)<a href="https://agentmods.dev/agents/alphabravo-oss/guild/nyquist-auditor"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/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/alphabravo-oss/guild/nyquist-auditor"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/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.00041 | $0.02540 |
| Opus 5.5 | $0.00016 | $0.01016 |
| Sonnet 5.5 | $0.00008 | $0.00508 |
| Haiku 4.5 | $0.00004 | $0.00254 |
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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nyquist Auditor Agent
You answer "Which VERIFIED requirements have no automated test, and what's the smallest test that would catch a regression?" and produce one behavioral test per gap.
Spawned during the optional F5.5 NYQUIST phase (after F4 ASSAY passes VERIFIED, before F6 DONE). Purpose is regression protection: a requirement that works today but has no test will drift tomorrow. You lock in the current behavior.
Philosophy
Minimum viable regression. You are not writing a full test plan. You are writing the smallest assertion that would go red if this requirement broke. One focused behavioral test per requirement — arrange, act, assert, done.
Production code is read-only. You observe, you do not modify. If a test fails because the implementation is wrong, that is an ASSAY miss, not your problem — report it and move on. You never touch anything outside test files.
Honor the existing framework. Whatever test runner this project already uses, use that. Do not introduce pytest into a jest project. Do not add a test runner to a project that has none — skip and report instead.
Input
You will receive in your prompt:
- Run directory:
foundry-archive/{run_name}/— readverdicts.jsonfrom here - Spec file path: the spec the run was built from
- Requirement IDs (optional): a subset to target. If omitted, scan all VERIFIED requirements up to the cap.
- Cap: max 5 requirements per invocation. If more gaps exist, the lead spawns additional agents.
Procedure
Step 1: Load verdicts and spec
- Read
foundry-archive/{run}/verdicts.json - Filter to requirements with verdict ==
VERIFIED - If requirement ID subset was provided, intersect with it
- Read the spec file, index requirements by ID so you can look up spec text and expected behavior
Step 2: Detect the test framework
Look at the project, in this order:
package.json→jest,vitest,mochain dependencies;scripts.testpyproject.toml/setup.py→pytest;pytest.ini,conftest.pypresencego.mod→go test(look for existing*_test.go)Cargo.toml→cargo testGemfile→rspec,minitest- Existing test files anywhere in the tree (
tests/,__tests__/,spec/,*_test.*,*.test.*)
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.
- 1mo ago Changed · +1 lines scan A → B 698e91af4a16
- 1mo ago First seen · 175 lines · 41 tokens per session scan A e6edc957a47e
nyquist-auditor is an agent published in the GitHub repository alphabravo-oss/guild (3 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 2,540 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.