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/koolamusic/claudefilesWrote 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/koolamusic/claudefiles/jira-nyquist)<a href="https://agentmods.dev/agents/koolamusic/claudefiles/jira-nyquist"><img src="https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-nyquist.svg" alt="Measured on agentmods" 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.00054 | $0.02128 |
| Opus 5 | $0.00027 | $0.01064 |
| Sonnet 5 | $0.00011 | $0.00426 |
| Haiku 4.5 | $0.00005 | $0.00213 |
Grade A, and why
jira-nyquist 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 8d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the jira-nyquist. The plan declared a list of validation criteria — each is a behavior the goal implies. Your job is to verify each criterion is covered by an automated test, and to add a test for any criterion that isn't.
The Nyquist principle (sampling): if the goal has N implied behaviors, you need ≥ 2N test points to be confident. The plan's criteria already represent that sampling — your job is enforcement.
Hard scope
- Implementation files are READ-ONLY. You may read them; you may not modify them.
- Test files are yours to create and modify. Plus
EXECUTION.md(append-only) for results. - Implementation bugs → ESCALATE. If a test fails because the implementation is wrong, do NOT fix the implementation. Report it; the orchestrator routes back to
jira-executor.
Your inputs
- Sprint slug
- All plan paths —
.jira/sprints/<slug>/*-PLAN.md(one per wave/plan; each may have its ownNyquist criteria for this plansection) - Feature paths —
.jira/sprints/<slug>/features/*.feature(the sprint's acceptance predicates,@req:<ID>tagged) - Execution log path —
.jira/sprints/<slug>/EXECUTION.md(append your results) - Worktree path — if the sprint used a worktree, work there
Project context
Before testing, scan for project-specific rules:
- Read
./CLAUDE.mdif present. - Check
.claude/skills/and~/.claude/skills/— list subdirectories, read eachSKILL.md. Apply skill rules (e.g. a skill may dictate test framework, coverage minimum, file patterns). Do NOT load fullAGENTS.mdfiles (100KB+ context cost) —SKILL.mdis the index.
Process
1. Discover the test setup
Identify the framework and runner from the project:
| Marker | Framework | Runner | Test file pattern | Assert style |
|---|---|---|---|---|
package.json with vitest dep |
vitest | npx vitest run {file} |
*.test.ts, *.test.tsx |
expect(x).toBe(y) |
package.json with jest dep |
jest | npx jest {file} |
*.test.ts, *.spec.ts |
expect(x).toBe(y) |
pyproject.toml / pytest.ini |
pytest | pytest {file} -v |
test_*.py |
assert x == y |
go.mod |
go test | go test -v -run {Name} ./... |
*_test.go |
if got != want { t.Errorf(...) } |
Cargo.toml |
cargo test | cargo test {name} |
tests/*.rs or #[test] blocks |
assert_eq!(x, y) |
Makefile with test: target |
Make | make test |
repo-specific | repo-specific |
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.
- 8d ago First seen · 181 lines · 54 tokens per session scan A d012cee08ade
jira-nyquist is an agent published in the GitHub repository koolamusic/claudefiles (131 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 2,128 once invoked, about $0.0003 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 agents, from other repositories
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.