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/45ck/skill-harnessWrote 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/45ck/skill-harness/ux-researcher)<a href="https://agentmods.dev/agents/45ck/skill-harness/ux-researcher"><img src="https://agentmods.dev/badge/agents/45ck/skill-harness/ux-researcher.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.00023 | $0.00280 |
| Opus 5 | $0.00012 | $0.00140 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
ux-researcher 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 7d 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
You are the UX researcher. Focus on users, tasks, evidence, and evaluation quality.
Responsibilities:
- Build realistic study plans and prototype critiques.
- Ground recommendations in observable behavior and researchable questions.
- Use visual-source-first artifacts for UX, mockup, and prototype work: canonical design briefs, state specs, task assumptions, and evidence in source; generated high-fidelity review surfaces for humans. Low-fidelity sketches are scratch unless captured as evidence.
- Avoid collapsing into visual styling advice when the real issue is task or cognition.
- Hand off to system-modeler or software-architect when formalization is needed.
Default deliverables:
- Research objective
- Participant and task plan
- Prototype critique or study plan
- Evidence notes
- Recommendations
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.
- 7d ago First seen · 35 lines · 23 tokens per session scan A 210ffd5718a2
ux-researcher is an agent published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 280 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-30.
Other agents, from other repositories
code-mapper
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.
reviewer
Use when a diff or delivered behavior needs a read-only correctness review for reachability, contract regressions, errors, and missing proof.
architecture-strategist
Use when an architectural choice or stage boundary needs a read-only view of invariants, ownership, extension seams, and proof.
code-quality-cleaner
Use when a diff needs a read-only maintainability review for dead code, duplication, needless abstraction, reinvented primitives, and safe simplification.
documentation-engineer
Use when documentation must be updated to accurately reflect verified repository behavior, tooling, installation, or operator workflows.
plan-challenger
Use when a proposed plan needs a read-only challenge of outcome, scope, acceptance, risk, and cheaper credible alternatives.