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 skills add sonature-lab/timsquad --skill tsq-planninggit clone --depth 1 https://github.com/sonature-lab/timsquadWrote 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/sonature-lab/timsquad/tsq-planning)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/tsq-planning"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-planning/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/skills/sonature-lab/timsquad/tsq-planning"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-planning.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.00065 | $0.00533 |
| Opus 5 | $0.00032 | $0.00267 |
| Sonnet 5 | $0.00013 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
tsq-planning 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
Planning
기획 문서 작성 및 요건 정의를 위한 가이드라인.
Philosophy
- SSOT 구조 준수: PRD (Why) → Planning (Overview) → Requirements (What)
- 각 문서는 다음 단계의 입력
- 검증 가능한 요건만 작성
Resources
| Priority | Type | Resource | Description |
|---|---|---|---|
| HIGH | ref | prd-guide | PRD 작성 가이드 + 예시 |
| HIGH | ref | requirements-guide | 요건 분류 + SMART + MoSCoW |
Quick Rules
SSOT Documents
| 문서 | 역할 |
|---|---|
prd.md |
왜 만드는지, 목표, 성공 지표 |
planning.md |
전체 계획, 마일스톤, 일정 |
requirements.md |
기능/비기능 요건 목록 |
functional-spec.md |
기능 시나리오, 예외처리 |
Large Document Strategy
800줄 이상 예상 문서는 반드시 분할:
- 목차 기반 규모 사전 추정
- 도메인별 분할
- 인덱스 파일에서 분할 문서 링크 유지
- 순차 append 방식으로 섹션별 작성
Context Verification
SSOT 템플릿 작성 시 config.yaml 프로젝트 설정을 먼저 확인.
프로젝트에서 실제 사용하는 서비스만 포함. 제너릭 외부 서비스를 무분별하게 채우지 않는다.
Checklist
| Priority | Item |
|---|---|
| CRITICAL | 목표가 명확히 정의되었는가 |
| CRITICAL | 스코프가 명확히 구분되었는가 (포함/제외) |
| HIGH | 모든 요건에 우선순위가 있는가 |
| HIGH | 요건이 검증 가능한가 (정량적 기준) |
| MEDIUM | 이해관계자 승인을 받았는가 |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 59 lines · 65 tokens per session scan A 5431e63ec99a
tsq-planning is a skill published in the GitHub repository sonature-lab/timsquad (11 stars, last pushed 10d ago), licensed MIT. It adds 65 tokens to every session and 533 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
write-prd
Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks.
product-frameworks
Product management frameworks for business cases, market analysis, strategy, prioritization, OKRs/KPIs, personas, requirements, and user research. Use when building ROI projections, competitive analysis, RICE scoring, OKR trees, user personas, PRDs, or usability testing plans.
prd-authoring
Standard for authoring product PRDs in docs/prd/: state the problem, users, requirements, and success; assign PRD-{AREA}-{NN} IDs; link down to specs.
requirement-engineering
Skill for requirement analysis and PRD writing — stakeholder identification, user story mapping, acceptance criteria, PRD structure, and risk analysis.
to-prd
Use when synthesizing a Product Requirements Document (PRD) from prior session evidence (replay logs, ADRs, evidence captures, prior PRDs) and routing it through a panel-of-experts review instead of a live user-feedback loop.
requirement-study
Analyze, write, and validate software requirements from any input — conversations, documents, rough notes, or existing specs. Use when someone asks to study requirements, create a PRD, analyze a feature request, extract requirements from a document, or validate completeness of existing requirements. Also triggers on…