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 joris887/exosuit --skill uat-cyclegit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/uat-cycle)<a href="https://agentmods.dev/skills/joris887/exosuit/uat-cycle"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/uat-cycle.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.00027 | $0.01777 |
| Opus 5 | $0.00014 | $0.00889 |
| Sonnet 5 | $0.00005 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
UAT-cycle 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UAT-cycle
Executing UAT cycle: $ARGUMENTS
Phase 1: Select Test Case
If a test case ID was provided (e.g., UAT-001):
- Read
docs/testing/UAT_COVERAGE.md - Find the test case by ID
- Present it to the user:
- Test Case ID: UAT-###
- Title: [title]
- Covers: [backlog story IDs or feature area]
- Prerequisites: [what's needed]
- Steps: [numbered steps]
- Acceptance Criteria: [checklist]
- Ask: "Ready to start testing? Are all prerequisites met?"
If a description was provided instead of an ID:
- Read
docs/testing/UAT_COVERAGE.md - Find the best matching test case(s)
- If ambiguous, present options for the user to choose
- Once selected, present as above
If no argument was provided:
- Read
docs/testing/UAT_COVERAGE.md - Show the status summary table
- List all test cases with status "Not Tested" (prioritized) or "Fail" (for retesting)
- Ask the user to select which test case to execute
Phase 2: Execute Test
Persona Context Loading
If the test case's parent story has a Personas: field (not "internal"), load the referenced persona(s) from docs/context/personas.md. When persona context is available:
- Frame test guidance from the persona's perspective — use their context (device, proficiency, constraints) to inform how the test should be performed
- Present steps with persona awareness — e.g., "As [Name] ([Role]), try to [step]. Given their [constraint], watch for [specific friction point]."
- Evaluate results against the persona's EVALUATES BY questions in addition to the acceptance criteria
- Flag FAILURE LOOKS LIKE matches — if a test result resembles the persona's failure scenario, escalate severity
Skip when: No Personas: field on the story, personas.md doesn't exist, or the test case is purely technical (API contract, data migration, etc.).
Test Execution
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.
- 8d ago First seen · 187 lines · 27 tokens per session scan A 7738c452cef5
UAT-cycle is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 19d ago), licensed MIT. It adds 27 tokens to every session and 1,777 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
Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
world-class-development-team
Operate a hierarchical software-development team of up to ten agents to understand a codebase, turn product requirements and bug reports into safe production-ready changes, and verify the result end to end. Use for multi-file feature implementation, bug fixing, refactoring, migrations, integrations, performance…
better-testing
Review and improve how tests protect critical software behavior. Use when assessing missing unit, integration, contract, or end-to-end coverage; flaky tests; weak assertions; happy-path-only tests; excessive mocking; implementation-coupled tests; low-value snapshots; slow suites; or code that is difficult to test…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.