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/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/nyquist-auditor)<a href="https://agentmods.dev/agents/vkirill/claude-lane-stack/nyquist-auditor"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/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/vkirill/claude-lane-stack/nyquist-auditor"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/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.00057 | $0.00195 |
| Opus 5.5 | $0.00023 | $0.00078 |
| Sonnet 5.5 | $0.00011 | $0.00039 |
| Haiku 4.5 | $0.00006 | $0.00019 |
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 4d 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.
What it actually says
nyquist-auditor
For each promise of the phase: the checks that prove it, whether they would fail without the work (mutate one line in a throwaway copy), whether an edge is unsampled (empty, maximum, unicode, concurrency). List the missing checks with the command each should be.
Read-only on product code unless the PM names a file you write. Report by path what you wrote.
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.
- 4d ago First seen · 17 lines · 57 tokens per session scan A d3a1d099f5cd
nyquist-auditor is an agent published in the GitHub repository VKirill/claude-lane-stack (124 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 195 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-10-25.
Other agents, from other repositories
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
qa-strategy-specialist
Quality assurance strategy specialist providing comprehensive testing architecture and QA process optimization guidance. Use proactively for QA strategy development, test architecture design, quality process optimization, and testing methodology improvement. When you prompt this agent, describe exactly what you want…
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.
integration-tester
Independent dynamic verification agent. Runs the test suite, executes acceptance criteria commands, and verifies runtime behavior. Breaks the self-assessment cycle where the implementer verifies their own work. Reports with command output evidence.
test-writer
Generates comprehensive tests for code. Reads existing test patterns in the project and matches the style (Jest, Vitest, pytest, etc.). Covers happy paths, edge cases, error cases, and boundary conditions.
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.