Borrowing it
Nothing to install: this file belongs to jigglypop/gaesup-world. 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/jigglypop/gaesup-world/master/.codex/prompts/verify.mdgit clone --depth 1 https://github.com/jigglypop/gaesup-worldWrote 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/jigglypop/gaesup-world/verify)<a href="https://agentmods.dev/commands/jigglypop/gaesup-world/verify"><img src="https://agentmods.dev/badge/commands/jigglypop/gaesup-world/verify.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.00155 |
| Opus 5 | $0.00000 | $0.00077 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
verify 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 today.
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
검증
변경 범위를 덮는 가장 좁은 검증부터 실행하고 점차 넓힌다: 도메인 테스트(pnpm test -- src/core/<domain> --runInBand), 빌드 타입체크(pnpm exec tsc -p tsconfig.build.json --noEmit), 변경 파일만 lint. public API나 subpath를 변경했으면 publicApi.test.ts와 packageExports.test.ts를 추가로 실행하고 AGENTS.md에 나열된 동시 수정 대상 6개 파일을 확인한다. 실패 출력은 그대로 보고하고, 실행하지 않은 검증을 성공으로 보고하지 않는다. 기존 실패와 이번 slice가 만든 regression을 구분한다.
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.
- today First seen · 4 lines · 0 tokens per session scan A afcc68a5b7ca
verify is a command published in the GitHub repository jigglypop/gaesup-world (22 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 155 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-06.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
api-review
Review the current code or API against API design principles — identifies violations and suggests improvements.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
pn-audit-api
Surgical API design review — REST conventions, status codes, response shapes, validation, and schema leaks. Use standalone or as part of pn-backend-audit. Outputs a scored fix roadmap.