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 jerseycheese/agent-skills --skill test-workflowgit clone --depth 1 https://github.com/jerseycheese/agent-skillsWrote 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/jerseycheese/agent-skills/test-workflow)<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/test-workflow"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/test-workflow.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.00112 | $0.02781 |
| Opus 5 | $0.00056 | $0.01391 |
| Sonnet 5 | $0.00022 | $0.00556 |
| Haiku 4.5 | $0.00011 | $0.00278 |
Grade A, and why
test-workflow 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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to invoke (auto-trigger)
Invoke automatically whenever:
- Source files under
src/have been edited and a commit is about to happen - The user asks to verify, check, or run tests without specifying which suite
- Tests are mentioned as a blocker ("make sure tests pass before merging")
Do NOT invoke for: documentation-only edits, config-only changes, or when the user explicitly says to skip tests.
Intelligent Test Workflow Coordinator
When to Use This Skill
Use this skill when:
- You've made code changes and need to run tests
- Unsure which test suite is appropriate (unit, E2E, visual, all?)
- Want smart test selection based on changed files
- Need coordinated test execution with dev server awareness
What This Skill Does
Analyzes your changes and intelligently runs the appropriate test suite(s):
- Unit tests for logic, utilities, hooks
- E2E tests for user flows and integration
- Visual regression for UI component changes
- CSS lint for style changes
- Full suite for widespread changes
Usage Flow
Phase 1: Analyze Changes
Detect what changed:
# Get changed files (staged or unstaged)
git diff --name-only HEAD
git diff --cached --name-only
# Or compare against branch
git diff develop...HEAD --name-only
Categorize changes:
📝 **Changed Files Analysis**
Component files: 3
- src/components/UserProfile.tsx
- src/components/Dashboard.tsx
- src/components/common/Button.tsx
Test files: 2
- src/components/UserProfile.test.ts
- src/components/Dashboard.test.ts
Style files: 1
- src/styles/dashboard.css
Utility files: 0
E2E test files: 0
Phase 2: Recommend Test Strategy
Based on changes:
## Recommended Test Strategy
### Why This Strategy
You've changed:
- 3 component files → Need unit tests + E2E tests
- 1 CSS file → Need CSS lint + visual regression
- Modified existing tests → They'll run automatically
### Recommended Test Suite
**Primary (Must Pass):**
1. Unit tests for changed components
2. CSS lint validation
3. TypeScript type check
**Secondary (Highly Recommended):**
4. E2E tests that use these components
5. Visual regression for Button component
**Optional (If Time Permits):**
6. Full test suite (confidence check)
### Execution Plan
```bash
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 · 468 lines · 112 tokens per session scan A 3958db8b21ce
test-workflow is a skill published in the GitHub repository jerseycheese/agent-skills (1 stars, last pushed 5d ago), licensed MIT. It adds 112 tokens to every session and 2,781 once invoked, about $0.0006 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
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
lamina-verify
Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify. Run isolated Persona and live UI audits; explicit verification is source-read-only.
lamina-evaluation
Judge product usability and evidence quality. Use when running Persona-based walkthroughs on a built product, planning an expert heuristic review, defining evidence-backed success metrics, or checking quantitative claims without inventing measurements. Use lamina-research to plan or synthesize evidence collection and…
recipe-eval-prompt
Compares original and optimized prompts through repeated blind paired execution in git worktrees. Use when evaluating prompt improvement effects or learning prompt engineering through concrete examples.
harness-validate
Use when user invokes /harness-validate or wants to check whether a harness.yaml file is valid according to the Harness Protocol v1 JSON Schema. Reports validation errors with field paths and helpful fix suggestions.
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.