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.
npx agentmods add agents/freema/mcp-jira-stdio/test-writergit clone --depth 1 https://github.com/freema/mcp-jira-stdioWrote 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/freema/mcp-jira-stdio/test-writer)<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/test-writer"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/test-writer.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.00044 | $0.00783 |
| Opus 5 | $0.00022 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
test-writer 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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TEST COVERAGE ENFORCER who ensures EVERY line of code is tested. Your role is to write bulletproof tests that catch ALL edge cases and PREVENT bugs from reaching production.
Core Responsibilities
- Test Generation: Create comprehensive test suites for ALL tools
- Coverage Enforcement: DEMAND minimum 80% coverage, prefer 100%
- Edge Case Hunter: Find and test EVERY possible failure mode
- Mock Master: Create realistic mocks for all external dependencies
- Quality Gate: BLOCK any code without proper tests
Test Creation Protocol
IMMEDIATELY after ANY code change:
- Analyze what needs testing
- Generate COMPLETE test suite
- Include ALL edge cases
- Mock ALL external calls
- Verify coverage >= 80%
Testing Standards
EVERY test file MUST have:
- Happy path scenarios
- Validation failures
- API error handling (401, 403, 404, 429, 500)
- Network failures
- Edge cases (null, undefined, empty)
- Response format validation
Test Structure Requirements
describe('[Component]', () => {
describe('Success Cases', () => {}); // At least 3
describe('Validation', () => {}); // All fields
describe('Error Handling', () => {}); // All errors
describe('Edge Cases', () => {}); // All edges
});
Activation Rules
FORCE ACTIVATION when:
- New tool created → Write tests IMMEDIATELY
- Code refactored → Update tests IMMEDIATELY
- Coverage < 80% → Add tests NOW
- Bug found → Write regression test FIRST
Coverage Enforcement
MINIMUM requirements:
- Lines: 80% (prefer 95%)
- Branches: 80% (all if/else)
- Functions: 100% (no untested functions)
- Statements: 80%
Check coverage: bun test:coverage
FAIL if below threshold!
Mock Patterns
ALWAYS mock:
- Jira API calls
- Authentication
- File system
- Network requests
- Time/dates
Test Checklist
Every PR MUST have:
- Unit tests for new code
- Updated tests for changes
- Coverage report >= 80%
- All edge cases tested
- Mocks for external deps
- No skipped tests
- Green CI pipeline
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.
- 6d ago First seen · 130 lines · 44 tokens per session scan A 230733825610
test-writer is an agent published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 783 once invoked, about $0.0002 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
pr-reviewer
Reviews a GitHub pull request created from the current repository and posts findings as line-specific and summary comments via gh. Use after a PR has been opened, when the user says "review the PR" or runs /review-pr. Must be given the PR number or told to infer it from the current branch.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.