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/specnpx skills add jh941213/codex-lattice --skill specgit 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)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/spec"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/spec.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 | $0.00058 | $0.00743 |
| Opus 5 | $0.00029 | $0.00371 |
| Sonnet 5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
spec 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bigseed — 86% identical, 384 lines differ
What it actually says
SPEC 기반 개발 - 인터뷰
SPEC 기반 개발 워크플로우입니다.
트리거
- "스펙", "spec", "명세서", "인터뷰", "기능 설계"
워크플로우
1단계: SPEC.md 확인 또는 생성
현재 디렉토리에 SPEC.md가 있는지 확인합니다.
- 있으면: 해당 파일을 읽고 인터뷰 시작
- 없으면: 사용자에게 기본 아이디어를 물어본 후 초안 생성
2단계: 심층 인터뷰
반드시 AskUserQuestion 도구를 사용하여 다음 영역에 대해 질문합니다:
-
기술적 구현
- 어떤 기술 스택을 사용할지
- 기존 코드베이스와의 통합 방법
- 성능 요구사항
-
UI & UX
- 사용자 흐름
- 디자인 패턴
- 접근성 요구사항
-
우려 사항
- 보안 고려사항
- 확장성 문제
- 유지보수 복잡도
-
트레이드오프
- 시간 vs 품질
- 단순함 vs 기능성
- 유연성 vs 성능
3단계: 질문 규칙
- 뻔한 질문 금지: "어떤 언어 쓸까요?" 같은 명확한 건 스킵
- 깊이 있게: 40개 이상 질문도 가능
- 연속 인터뷰: 완료될 때까지 계속 질문
- 한 번에 1-2개 질문: 사용자가 답변하기 쉽게
4단계: 명세서 작성
인터뷰 완료 후 SPEC.md 파일을 상세하게 업데이트합니다:
# [기능명] 명세서
## 개요
[한 문장 설명]
## 목표
- [ ] 목표 1
- [ ] 목표 2
## 기술 스택
- ...
## 상세 요구사항
### 기능적 요구사항
1. ...
### 비기능적 요구사항
1. ...
## UI/UX 명세
- ...
## API 설계 (해당 시)
- ...
## 데이터 모델 (해당 시)
- ...
## 보안 고려사항
- ...
## 테스트 계획
- ...
## 마일스톤
1. [ ] 단계 1
2. [ ] 단계 2
## 열린 질문 / 결정 필요
- ...
5단계: 안내
명세서 작성 후 사용자에게 안내:
"명세서가 완성되었습니다. 새 세션에서 다음 명령어로 구현을 시작하세요:"
SPEC.md 읽고 구현 시작해줘구현 완료 후 검증:
$spec-verify
핵심 원칙
- 컨텍스트 분리: 인터뷰 세션 ≠ 구현 세션
- 사용자 컨트롤: 질문을 통해 사용자가 방향을 결정
- 상세한 문서화: 다음 세션에서 바로 실행 가능한 수준
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.
- 4d ago First seen · 119 lines · 58 tokens per session scan A e8635887cf62
spec is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 743 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…