jira-nyquist

jira-nyquist is an agent for Claude Code from koolamusic/claudefiles. It costs 54 tokens per session (2,128 once invoked), scanned A, original, MIT.

A sprint test-checking agent that compares a software plan's stated requirements with its automated tests. A sprint is a planned piece of development work.

In plain words
What is it for?
Use it after sprint implementation to add missing tests and record validation results, without changing the implementation code.
Why use it?
It finds requirements that have no test coverage, so gaps can be reported before the work is considered complete.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions AGENTS.md.

Part of the jira plugin — 13 commands, 9 agents shipped together

Good fit Use it after sprint implementation to add missing tests and record validation results, without changing the implementation code.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/koolamusic/claudefiles/jira-nyquist
Install

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.

Clone the repo
git clone --depth 1 https://github.com/koolamusic/claudefiles

Made for: Claude Code.

Or install jira, the plugin that ships this one along with the rest of its 13 commands, 9 agents.

Wrote 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.

agentmods badge for jira-nyquist

README.md
[![agentmods](https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-nyquist.svg)](https://agentmods.dev/agents/koolamusic/claudefiles/jira-nyquist)
Your own site
<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>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,128 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash d012cee08ade, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

plugins/jira/agents/jira-nyquist.md · 181 lines

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

  1. Sprint slug
  2. All plan paths.jira/sprints/<slug>/*-PLAN.md (one per wave/plan; each may have its own Nyquist criteria for this plan section)
  3. Feature paths.jira/sprints/<slug>/features/*.feature (the sprint's acceptance predicates, @req:<ID> tagged)
  4. Execution log path.jira/sprints/<slug>/EXECUTION.md (append your results)
  5. Worktree path — if the sprint used a worktree, work there

Project context

Before testing, scan for project-specific rules:

  • Read ./CLAUDE.md if present.
  • Check .claude/skills/ and ~/.claude/skills/ — list subdirectories, read each SKILL.md. Apply skill rules (e.g. a skill may dictate test framework, coverage minimum, file patterns). Do NOT load full AGENTS.md files (100KB+ context cost) — SKILL.md is 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

Read the full file on GitHub · 181 lines

Changes

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.

  1. 8d ago First seen · 181 lines · 54 tokens per session scan A d012cee08ade

Subscribe to this mod's changes

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.

Related

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.

athola/claude-night-market · 38 tokens

sdd-init

Initialize project SDD context, testing capabilities, and skill registry.

Gentleman-Programming/gentle-pi · 17 tokens

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.

echoVic/blade-code · 51 tokens

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.

felvieira/claude-skills-fv · 66 tokens

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…

HirogaKatageri/hirokata · 77 tokens

implement-test-diversifier

Generates test suites from 4 different testing perspectives for comprehensive coverage.

eai-support/eai-gofer · 19 tokens