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-grillgit 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-grill)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/tsq-grill"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-grill/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-grill"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-grill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00241 | $0.01145 |
| Opus 5 | $0.00120 | $0.00573 |
| Sonnet 5 | $0.00048 | $0.00229 |
| Haiku 4.5 | $0.00024 | $0.00114 |
Grade A, and why
tsq-grill 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
/tsq-grill — 소크라틱 심층 인터뷰
질문을 통해 답을 끌어내는 소크라틱 방법론으로 PRD와 Sub-PRD를 작성한다. PRD가 부실하면 그 위에 세워지는 모든 것이 부실해진다.
Mode Detection (자동)
.timsquad/ssot/prd.md 존재?
├── NO → PRD Mode (프로젝트 전체 인터뷰)
└── YES → prd.md에 빈 섹션(TBD, TODO, 빈 테이블)이 있는가?
├── YES → PRD Reinforce Mode (빈 섹션 보강 인터뷰)
└── NO → Sub-PRD Mode (기능별 인터뷰)
명시적 모드: /tsq-grill prd | /tsq-grill sub | /tsq-grill (자동)
PRD Mode — 프로젝트 전체 인터뷰
PRD가 없거나 프로젝트 초기 단계에서 사용.
질문 트리는 references/interview-guide.md를 Read하여 참조한다.
인터뷰 원칙
- 질문 트리는 가이드이지 체크리스트가 아니다
- 이미 답변된 영역은 건너뛴다
- 한 번에 2-3개 질문만. 사용자가 부담을 느끼면 안 된다
- 프로젝트 특성에 맞는 질문을 추가한다
진행: Phase 1(비전) → Phase 2(스코프) → Phase 3(성공 지표) → PRD 생성 → 리뷰
PRD 생성 시 .timsquad/ssot/prd.md에 구조화:
비전/타겟/시장 → 기능 인덱스 테이블 → 제약사항 → KPI → Anti-scope → TBD
PRD Reinforce Mode — 기존 PRD 보강
- prd.md를 읽고 빈 섹션 / TBD 항목 목록을 사용자에게 제시
- 사용자가 보강할 항목 선택
- 해당 항목에 대해 소크라틱 인터뷰 진행
- 결과를 prd.md에 반영
- 사용자 리뷰 요청 (Human Checkpoint)
Sub-PRD Mode — 기능별 인터뷰
질문 트리는 references/interview-guide.md를 Read하여 참조한다.
- prd.md 기능 인덱스에서 Sub-PRD 미작성 기능 식별
- 사용자에게 대상 기능 확인
- Why → What → How 3단계 인터뷰
.timsquad/ssot/prd/[feature].md생성- prd.md 기능 인덱스 업데이트
질문 방식 원칙 (공통)
- 한 번에 질문 2-3개만 — 질문 폭탄은 대충 답하게 만든다
- 답변을 요약해서 확인 — 에이전트 해석이 맞는지 검증
- 모호하면 구체적 예시로 재질문 — "사용자 경험 개선"은 PRD에 쓸 수 없다
- "모르겠다"도 유효 — TBD로 기록 + 결정 시점 명시
- 가정하지 않는다 — 선택지 제시, 사용자가 고르게 한다
Output
| Mode | 산출물 |
|---|---|
| PRD | .timsquad/ssot/prd.md + 인터뷰 로그 |
| Reinforce | 보강된 prd.md (기존 유지, 빈 섹션만) |
| Sub-PRD | .timsquad/ssot/prd/[feature].md + 인덱스 업데이트 |
Rules
- 사용자 답변을 임의로 해석하지 않는다 — 확인 후 기록
- "아직 모르겠다"는 TBD + 결정 시점 명시
- SSOT 외 파일 수정 금지
- PRD/Sub-PRD 생성 후 반드시 사용자 리뷰 요청 (Human Checkpoint)
What ships with it
1 file 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 · 92 lines · 241 tokens per session scan A 357d406da49b
tsq-grill is a skill published in the GitHub repository sonature-lab/timsquad (11 stars, last pushed 10d ago), licensed MIT. It adds 241 tokens to every session and 1,145 once invoked, about $0.0012 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.
mk:grill
Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan".…
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.