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/rungchan2/frontend-skillsWrote 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/rungchan2/frontend-skills/run)<a href="https://agentmods.dev/commands/rungchan2/frontend-skills/run"><img src="https://agentmods.dev/badge/commands/rungchan2/frontend-skills/run.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.00000 | $0.00353 |
| Opus 5 | $0.00000 | $0.00177 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
run 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
E2E 테스트 실행
자연어 E2E 테스트를 실행합니다.
사용법
/e2e-testing:run- 전체 시나리오 테스트/e2e-testing:run auth- 파일명에 auth가 포함된 시나리오/e2e-testing:run 1- 1번 시나리오만/e2e-testing:run 1 3- 1번, 3번 시나리오/e2e-testing:run 1-3- 1~3번 시나리오
실행
.e2e/init.md에서 환경 설정(Base URL, 환경)을 읽으세요..e2e/credentials.md에서 테스트 계정 정보를 읽으세요. 없으면 유저에게 생성하라고 안내하세요..e2e/scenarios/디렉토리에서 시나리오 파일 목록을 확인하세요.- 인자에 맞는 시나리오를 선택하세요. 인자가 없으면 전체 시나리오를 실행하세요.
- 각 시나리오마다
e2e-tester서브 에이전트를 병렬로 Task tool로 실행하세요.- 프롬프트에 init.md 내용 + credentials.md 내용 + 시나리오 내용을 포함하세요.
- 모든 서브 에이전트 완료 후 결과를 취합하여
.e2e/results/{YYYY-MM-DD_HHmm}.md단일 파일로 저장하세요. - 유저에게 전체 결과를 테이블 형식으로 보고하세요.
$ARGUMENTS
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 · 24 lines · 0 tokens per session scan A c8068634b814
run is a command published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 353 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-08-31.
Other commands, from other repositories
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.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.