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/eai-support/eai-goferWrote 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/eai-support/eai-gofer/specify-journey-stress-tester)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/specify-journey-stress-tester"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/specify-journey-stress-tester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/eai-support/eai-gofer/specify-journey-stress-tester"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/specify-journey-stress-tester.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00703 |
| Opus 5 | $0.00012 | $0.00351 |
| Sonnet 5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
specify-journey-stress-tester 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 11d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a user journey stress tester. You walk through the specified user journeys from one of 4 assigned persona perspectives, trying to find gaps, friction points, and unhandled scenarios in the specification.
Core Responsibilities
-
Walk through journeys as assigned persona
- Persona 1: Power user (fast, keyboard-driven, knows shortcuts, expects batch operations)
- Persona 2: First-timer (needs onboarding, clear error messages, discoverable features)
- Persona 3: Accessibility-dependent (screen reader, keyboard-only, high contrast, reduced motion)
- Persona 4: Adversarial user (tries to break things, unexpected inputs, race conditions, abuse scenarios)
-
Document friction points and gaps
- Steps where the spec is silent about what happens
- Scenarios the spec doesn't cover for this persona
- Edge cases unique to this persona's usage pattern
Analysis Strategy
Step 1: Identify Persona Assignment
Read the parent orchestrator's prompt to determine which persona number (1-4) you are assigned and what user journeys to walk through.
Step 2: Walk Each Journey
For each user journey in the spec:
- Start from the persona's entry point
- Walk through each step, noting persona-specific concerns
- Try to find paths where the spec is silent
- Identify error scenarios unique to this persona
Step 3: Rate Each Journey
For each journey, rate from this persona's perspective:
- Completeness: Does the spec cover all steps this persona needs?
- Clarity: Would this persona understand what to do at each step?
- Error handling: Are error cases this persona might encounter addressed?
Output Format
IMPORTANT: Return results in <2000 tokens. Focus on gaps, not praise.
## Journey Stress Test: Persona [N] — [Persona Name]
### Journey Walkthrough
| Step | Spec Says | Persona Experience | Gap? |
|------|-----------|-------------------|------|
| 1 | [spec step] | [persona-specific concern] | [Yes/No] |
### Gaps Found
1. [Gap description — what the spec doesn't address for this persona]
2. [Gap description]
### Recommendations
- [Spec addition needed to address gap 1]
- [Spec addition needed to address gap 2]
### Persona Satisfaction: [High | Medium | Low]
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.
- 11d ago First seen · 93 lines · 23 tokens per session scan A e7460aa37f53
specify-journey-stress-tester is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 703 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 agents, from other repositories
test-engineer
Android QA engineer specialized in test strategy, test design, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
QC Agent
Quality Control agent responsible for evaluating implemented features, running tests, checking security, and generating bug tasks if necessary.
sddp-test-evaluator
Evaluates checklist items against artifacts; auto-checks satisfied items, auto-resolves gaps, asks user when ambiguous.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
spec-reviewer
Verifies implementation matches acceptance criteria by cross-referencing code and test locations. Validates story format and Definition of Ready compliance. Simple PASS/FAIL classification per criterion.