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 skills add Yoshikemolo/mcp-jira-devflow --skill test-executiongit clone --depth 1 https://github.com/Yoshikemolo/mcp-jira-devflowWrote 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/skills/yoshikemolo/mcp-jira-devflow/test-execution)<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/test-execution"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/test-execution.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.00028 | $0.00486 |
| Opus 5 | $0.00014 | $0.00243 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
test-execution 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.
What it actually says
Test Execution Skill
Run and manage automated tests.
Allowed Operations
- Run unit tests
- Run integration tests
- Run specific test files
- Run tests by pattern
- Generate coverage reports
- View test results
Forbidden Operations
- Modify test files during execution
- Skip tests without documentation
- Disable coverage thresholds
- Run tests against production
- Commit test snapshots without review
Constraints
- Tests must run in isolated environment
- No network calls to external services (use mocks)
- Test timeout: 30 seconds per test
- Coverage minimum: 80%
Test Categories
| Type | Speed | Dependencies | When to Run |
|---|---|---|---|
| Unit | Fast | Mocked | Every commit |
| Integration | Medium | Test fixtures | Before merge |
| E2E | Slow | Full stack | Before release |
Quick Commands
# Run all tests
npm test
# Run with coverage
npm run test:coverage
# Run specific file
npm test -- path/to/test.ts
# Run by pattern
npm test -- --grep "auth"
For detailed test patterns, see TEST-PATTERNS.md.
For coverage configuration, see COVERAGE-GUIDE.md.
Output Format
{
"passed": 42,
"failed": 0,
"skipped": 2,
"duration": 1234,
"coverage": {
"lines": 85.5,
"branches": 80.2
}
}
Failure Handling
- Capture full error output
- Include stack traces
- Show relevant code context
- Suggest potential fixes if obvious
Example Usage
Run all unit tests
Run tests matching "auth"
Run tests with coverage report
Show results of last test run
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 28 tokens per session scan A 64e961fdb2ef
test-execution is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 486 once invoked, about $0.0001 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-31.
Other skills, from other repositories
testing-python
Stratégie de Tests Python 3.14+. Use when writing tests, reviewing test coverage, or setting up testing.
testing-symfony
Stratégie de Tests Symfony 8.1 / PHP 8.5. Use when writing tests, reviewing test coverage, or setting up testing.
testing-reactnative
Testing React Native 0.85+. Use when writing tests, reviewing test coverage, or setting up testing.
testing-patterns
Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.
testing
TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.