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/Dannykkh/skill-olympusWrote 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/dannykkh/skill-olympus/minos)<a href="https://agentmods.dev/commands/dannykkh/skill-olympus/minos"><img src="https://agentmods.dev/badge/commands/dannykkh/skill-olympus/minos/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dannykkh/skill-olympus/minos"><img src="https://agentmods.dev/badge/commands/dannykkh/skill-olympus/minos.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00718 |
| Opus 5.5 | $0.00012 | $0.00287 |
| Sonnet 5.5 | $0.00006 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
minos 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 1mo 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.
This is a copy
84% identical to design-review — 152 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/minos
QA 시나리오를 Playwright 테스트로 변환하고, 모든 테스트가 통과할 때까지 자동 수정을 반복합니다.
실행 절차
skills/minos/SKILL.md를 읽어 전체 워크플로우를 파악합니다.- 7단계 워크플로우를 순서대로 실행합니다:
- Step 1: 시나리오 수집 ($ARGUMENTS가 있으면 해당 파일, 없으면 자동 탐색)
- Step 2: Playwright 코드 생성 (references/playwright-codegen.md 참조)
- Step 3: 서버 준비
- Step 4: 테스트 실행
- Step 5: 브라우저 탐색 QA (references/browser-explorer.md 참조, 탐색 스크립트 생성·실행 → 이슈 회수.
--explore-mcp시 Playwright MCP fallback) - Step 6: Healer Loop (references/healer-loop.md 참조)
- Step 7: 결과 보고
- 각 단계에서 실패하면 사용자에게 보고하고 다음 단계 진행 여부를 확인합니다.
사용 예시
/minos # 자동 감지
/minos @qa-scenarios.md # 특정 QA 문서
/minos --api-only # API 테스트만
/minos --ui-only # UI 테스트만
/minos --max-retries 3 # 최대 3회 반복
/minos --fix-test-only # 구현 코드 수정 금지
/minos --explore-only # 브라우저 탐색 QA만 실행
/minos --no-explore # 브라우저 탐색 QA 스킵
/minos --no-explore-active # 탐색 QA 패시브 수집만 (인터랙션 스킵)
/minos --explore-mcp # 탐색 QA를 Playwright MCP 방식으로 (fallback)
탐색 QA(Step 5)는 기본적으로 탐색 스크립트(
tests/explore/*.spec.ts)를 생성·실행하고 결과report.json에서 이슈만 추출합니다. Playwright만 있으면 동작하며, MCP 도구는--explore-mcpfallback에서만 사용됩니다.
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.
- 1mo ago First seen · 41 lines · 30 tokens per session scan A d7fe32879b58
minos is a command published in the GitHub repository Dannykkh/skill-olympus (7 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 718 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to design-review, differing in 152 lines, and is treated as a copy.
Other commands, from other repositories
playwright-setup
Verify Playwright CLI installation and create a .playwright/cli.config.json configuration file. Use when setting up browser automation, configuring Playwright, or user mentions "setup playwright", "configure browser testing", "install playwright".
web-runtime-verify
Verify a built web frontend at runtime: serve the build, assert page identity, run the web battery (overflow 320 to 2560, keyboard, console, Lighthouse, axe), and decide a PASS/FAIL/BLOCKED gate. Fixes are routed, not applied. Do not use to plan (implementation-plan), write code (implement-approved-slice), for perf…
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
record
Record the browser while validating a flow, then judge it against a rubric.
verify-work
Validate built features through conversational UAT.