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/znlnzi/claude-config-studio/e2egit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/e2e)<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/e2e"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/e2e.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.00011 | $0.00303 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
e2e 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 4d 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
/e2e - 端到端测试
使用 Playwright 生成和运行 E2E 测试。
工作流
1. 分析目标
- 识别要测试的用户流程
- 确定关键交互点
- 列出预期结果
2. 生成测试
- 使用 Playwright API
- 使用语义选择器优先（role, label, text）
- 添加 data-testid 作为后备
3. 运行测试
- 执行测试套件
- 捕获失败截图
- 记录测试结果
测试结构
import { test, expect } from '@playwright/test';
test.describe('功能名称', () => {
test('用户场景', async ({ page }) => {
// 导航
await page.goto('/path');
// 交互
await page.getByRole('button', { name: '提交' }).click();
// 断言
await expect(page.getByText('成功')).toBeVisible();
});
});
最佳实践
- 测试真实用户流程，不测试实现细节
- 使用 Page Object 模式组织代码
- 每个测试独立运行，不依赖其他测试
- 使用 fixtures 管理测试数据
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.
- 4d ago First seen · 51 lines · 11 tokens per session scan A 426ffaf35b28
e2e is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 303 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 commands, from other repositories
paul:verify
Guide manual user acceptance testing of recently built features.
a11y-audit
Audit Accessibilité WCAG 2.2 AAA.
fix
Correction automatisee des bugs identifies par la QA Recette.
recette
Tests d'acceptance automatises avec Claude in Chrome.
regression
Voir et gerer le registre de tests de regression QA Recette.
test-suite
Run comprehensive test suite with coverage analysis.