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 agentmods add commands/brianmontero18/dev-mcp-tools/quxgit clone --depth 1 https://github.com/brianmontero18/dev-mcp-toolsWrote 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/commands/brianmontero18/dev-mcp-tools/qux)<a href="https://agentmods.dev/commands/brianmontero18/dev-mcp-tools/qux"><img src="https://agentmods.dev/badge/commands/brianmontero18/dev-mcp-tools/qux.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 | $0.00000 | $0.00516 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
qux 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 3d 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
QUX - UX Testing Scenarios
When user types "qux", execute this workflow:
Mindset: Human UX Tester
Imagine you are a human UX tester of the feature you just implemented.
1. Generate Test Scenarios
Create a comprehensive list of scenarios you would test, covering:
- Happy paths: Normal user flows
- Edge cases: Boundary conditions
- Error states: What happens when things go wrong
- Accessibility: Screen readers, keyboard navigation
- Performance: Large datasets, slow networks
- Mobile/responsive: Different screen sizes
- Cross-browser: Different browsers/devices
2. Prioritization
Sort scenarios by highest priority:
- Critical: Core functionality that must work
- High: Important user flows
- Medium: Nice-to-have features
- Low: Edge cases that rarely occur
Response Template
👤 **QUX - UX Testing Scenarios**
**Feature Tested:** [Feature name and brief description]
## 🔴 CRITICAL Priority
- [ ] **Scenario**: [Description]
- **Steps**: 1. [step] 2. [step] 3. [step]
- **Expected**: [expected result]
- **Risk**: [what breaks if this fails]
## 🟠 HIGH Priority
- [ ] **Scenario**: [Description]
- **Steps**: [steps]
- **Expected**: [expected result]
## 🟡 MEDIUM Priority
- [ ] **Scenario**: [Description]
- **Steps**: [steps]
- **Expected**: [expected result]
## 🟢 LOW Priority
- [ ] **Scenario**: [Description]
- **Steps**: [steps]
- **Expected**: [expected result]
## ♿ Accessibility Scenarios
- [ ] Screen reader navigation
- [ ] Keyboard-only navigation
- [ ] High contrast mode
- [ ] Text scaling (200%+)
## 📱 Mobile/Responsive
- [ ] Mobile portrait/landscape
- [ ] Tablet view
- [ ] Desktop breakpoints
## ⚡ Performance Scenarios
- [ ] Large dataset handling
- [ ] Slow network conditions
- [ ] Offline behavior
**Total Scenarios**: [count]
**Estimated Testing Time**: [hours/days]
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.
- 3d ago First seen · 70 lines · 0 tokens per session scan A c5cca40429a5
qux is a command published in the GitHub repository brianmontero18/dev-mcp-tools (0 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 516 tokens. 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-09-01.
Other commands, from other repositories
playwright
Write or update Playwright E2E tests following project conventions.
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
paul:verify
Guide manual user acceptance testing of recently built features.
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.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
plan-spec
仅在人工明确安排 UI 自动化时，根据任务、产品规则或原型生成独立行为 Spec.