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 skills/jh941213/codex-lattice/spec-verifynpx skills add jh941213/codex-lattice --skill spec-verifygit clone --depth 1 https://github.com/jh941213/codex-latticeWrote 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/skills/jh941213/codex-lattice/spec-verify)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/spec-verify"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/spec-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.00057 | $0.00723 |
| Opus 5 | $0.00028 | $0.00362 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
spec-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 6d 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
SPEC 검증
명세서 기반 작업 완료 후 검증하는 스킬입니다.
트리거
- "스펙 검증", "spec-verify", "명세서 검증", "구현 검증"
워크플로우
1단계: 검증 경로 선택
기본은 현재 세션에서 읽기 전용으로 검증한다. 사용자가 서브에이전트 사용을 명시했거나 현재 Codex 지침상 허용되면 explorer 또는 qa 역할로 분리한다.
검증 프롬프트:
SPEC.md 파일을 읽고 다음을 검증하세요:
1. 명세서의 모든 요구사항이 구현되었는지 확인
2. 각 항목별 체크:
- [ ] 기능적 요구사항
- [ ] 비기능적 요구사항
- [ ] UI/UX 명세
- [ ] API 설계 (해당 시)
- [ ] 보안 고려사항
3. 누락된 항목이 있으면 구체적으로 명시
4. 개선 제안 사항 포함
결과를 SPEC-REVIEW.md 파일로 작성하거나 사용자에게 요약하세요.
2단계: 피드백 반영
검증 결과에 누락 사항이 있으면:
- SPEC-REVIEW.md 내용을 사용자에게 보여줌
- 수정 여부 확인 (AskUserQuestion 사용)
- 승인 시 누락 사항 구현
3단계: 완료 보고
모든 항목이 완료되면:
## 검증 완료
### 구현 상태
- [x] 기능적 요구사항: 100%
- [x] 비기능적 요구사항: 100%
- [x] UI/UX: 100%
- [x] 테스트: 100%
### 주의사항
- ...
### 다음 단계 제안
- ...
검증 체크리스트
## SPEC 검증 체크리스트
### 기능 완성도
- [ ] 모든 기능적 요구사항 구현됨
- [ ] 모든 엣지 케이스 처리됨
- [ ] 에러 핸들링 적절함
### 코드 품질
- [ ] 타입 안전성 확보
- [ ] 린트 규칙 준수
- [ ] 테스트 커버리지 충분
### 문서화
- [ ] 코드 주석 적절
- [ ] API 문서 (해당 시)
- [ ] README 업데이트
### 보안
- [ ] 입력 검증
- [ ] 인증/권한 확인
- [ ] 민감 정보 보호
핵심 원칙
- 객관적 검증: 명세서 대비 실제 구현 비교
- 구체적 피드백: "안 됨" 대신 "X 기능의 Y 부분 누락"
- 반복 가능: 피드백 → 수정 → 재검증 사이클
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.
- 6d ago First seen · 97 lines · 57 tokens per session scan A 68b82fc5ca21
spec-verify is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 723 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…