Borrowing it
Nothing to install: this file belongs to whchoi98/seoul-opendata-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/whchoi98/seoul-opendata-mcp/main/.claude/commands/test-all.mdgit clone --depth 1 https://github.com/whchoi98/seoul-opendata-mcpWrote 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/whchoi98/seoul-opendata-mcp/test-all)<a href="https://agentmods.dev/commands/whchoi98/seoul-opendata-mcp/test-all"><img src="https://agentmods.dev/badge/commands/whchoi98/seoul-opendata-mcp/test-all/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/whchoi98/seoul-opendata-mcp/test-all"><img src="https://agentmods.dev/badge/commands/whchoi98/seoul-opendata-mcp/test-all.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.00009 | $0.00508 |
| Opus 5 | $0.00005 | $0.00254 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
test-all 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 10d 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
Test All
이 프로젝트의 전체 테스트 스위트를 실행합니다.
Step 1: 테스트 프레임워크 감지
프로젝트 파일을 읽어 테스트 프레임워크 결정:
package.json-> test 스크립트 찾기 (vitest, jest, mocha 등)vitest.config.ts또는vite.config.ts확인
Step 2: 테스트 실행
적절한 테스트 커맨드 실행:
npm test
Live 테스트 (선택사항)
실제 Seoul Open Data API에 대한 live 테스트를 실행하려면:
RUN_LIVE=true npm test
또는 live-sweep 스크립트 사용:
npm run bundle
# MCPB 번들에 포함된 live-sweep 실행
Step 3: 결과 보고
다음을 제시합니다:
- 실행된 총 테스트 수, 통과, 실패, 건너뜀
- 실패한 테스트의 상세 내용 (파일 경로 및 오류 메시지)
- 명백한 원인이 있으면 실패한 테스트에 대한 수정 제안
Error Recovery
테스트 러너 자체 실패 시
npm run build # 빌드 확인
npm test # 다시 시도
일반적인 실패 패턴 및 수정
| 실패 패턴 | 가능성 있는 원인 | 수정 방법 |
|---|---|---|
| "file not found" | 재구조화 후 누락된 파일 | 파일 생성 또는 테스트 업데이트 |
| "invalid JSON" | 잘못된 fixture 포맷 | python3 -m json.tool <file> |
| "Version mismatch" | package.json과 manifest.json 버전 불일치 | 둘 다 같은 버전으로 업데이트 |
| "타입 에러" | TypeScript 타입 불일치 | npm run build 에러 메시지 확인 |
많은 테스트가 동시에 실패하는 경우
구조적 변경으로 여러 가정이 깨진 것일 가능성:
git log -1— 마지막 변경사항은?git diff HEAD~1— 구체적으로 무엇이 변경되었나?- 개별 테스트가 아닌 근본 원인 수정
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.
- 10d ago First seen · 66 lines · 9 tokens per session scan A 8b718f46137a
test-all is a command published in the GitHub repository whchoi98/seoul-opendata-mcp (1 stars, last pushed 25d ago), licensed MIT. It adds 9 tokens to every session and 508 once invoked, about $0.0000 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.