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-inspectgit 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-inspect)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/tsq-inspect"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-inspect/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-inspect"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-inspect.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.00207 | $0.01247 |
| Opus 5 | $0.00103 | $0.00624 |
| Sonnet 5 | $0.00041 | $0.00249 |
| Haiku 4.5 | $0.00021 | $0.00125 |
Grade A, and why
tsq-inspect 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tsq-inspect — 파이프라인 전체 건강 점검
릴리스 전, 대규모 작업 후, 또는 "뭔가 이상하다" 싶을 때 실행하는 종합 진단. 데드코드와 죽은 프로세스는 시간이 지나면 반드시 누적된다 — 정기적으로 제거해야 파이프라인이 건강하다.
Protocol
- 데이터 수집: 아래 7개 영역을 자동 점검 (CLI + 파일 스캔)
- 리포트 생성: 영역별 PASS/WARN/FAIL + 구체적 항목
- 권고 제시: 수정 방법과 우선순위
- 사용자 확인: 자동 수정 가능한 항목은 동의 후 즉시 처리
점검 7영역
1. Hook 정합성
settings.json에 등록된 Hook vs 실제 스크립트 파일 대조.
| 점검 | 방법 |
|---|---|
| 유령 Hook | settings.json에 등록됐지만 스크립트 파일 없음 |
| 고아 스크립트 | scripts/ 디렉토리에 있지만 settings.json에 미등록 |
| Fail 전략 불일치 | || true 유무와 의도된 fail-closed/open 비교 |
2. 스킬 정합성
templates/base/skills/ vs 배포된 .claude/skills/ 대조.
| 점검 | 방법 |
|---|---|
| 고아 스킬 | 디렉토리 존재하지만 SKILL.md 없음 |
| Frontmatter 누락 | name 또는 description 빠짐 |
| 120줄 초과 | Progressive Disclosure 기준 위반 |
| references/ 포인터 끊김 | SKILL.md에서 참조하지만 파일 없음 |
| 미배포 스킬 | config의 SKILL_PRESETS에 없고 BASE_SKILLS에도 없음 |
3. CLI 정합성
src/index.ts 등록 vs src/commands/ 파일 대조.
| 점검 | 방법 |
|---|---|
| 미등록 커맨드 | src/commands/*.ts 있지만 index.ts에 import 없음 |
| 유령 import | index.ts에 import 있지만 파일 없음 |
| 빌드 동기화 | src/ vs dist/ 타임스탬프 비교 |
4. 문서 Drift
보완계획/SSOT 문서의 주장 vs 실제 수치 대조.
| 점검 | 방법 |
|---|---|
| Hook 수 불일치 | 문서 주장 vs settings.json 실제 수 |
| 스킬 수 불일치 | 문서 주장 vs 실제 디렉토리 수 |
| 테스트 수 불일치 | 문서 주장 vs npm test 실제 수 |
| CLI 수 불일치 | 문서 주장 vs index.ts 등록 수 |
| 로드맵 상태 | 이슈 상태(open/closed) vs 문서 "완료/미착수" |
상세 점검 항목은 references/checklist.md를 Read하여 참조.
5. 테스트 커버리지 갭
소스 파일 대비 테스트 파일 존재 여부.
| 점검 | 방법 |
|---|---|
| 테스트 없는 소스 | src/**/*.ts에 대응하는 *.test.ts 없음 |
| 빈 테스트 | .test.ts 존재하지만 describe/it 블록 없음 |
6. 설정 일관성
config.json, package.json, tsconfig.json 간 교차 검증.
| 점검 | 방법 |
|---|---|
| 버전 불일치 | package.json vs config.json framework_version |
| 스택 불일치 | config.json stack vs 실제 dependencies |
| 스크립트 누락 | test/build 스크립트 미정의 |
7. 상태 파일 위생
.timsquad/state/ 디렉토리의 정합성.
| 점검 | 방법 |
|---|---|
| 좀비 토큰 | controller-active 존재하지만 Controller 미실행 |
| Stale workflow | workflow.json의 current_phase와 current-phase.json 불일치 |
| 깨진 JSONL | decisions.jsonl에 유효하지 않은 JSON 행 |
| 잔여 임시 파일 | *.tmp, *.bak 등 |
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.
- 9d ago First seen · 109 lines · 207 tokens per session scan A 77629b693990
tsq-inspect is a skill published in the GitHub repository sonature-lab/timsquad (11 stars, last pushed 9d ago), licensed MIT. It adds 207 tokens to every session and 1,247 once invoked, about $0.0010 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
phase-8-review
Verify codebase quality — architecture consistency, convention compliance, gap analysis. Triggers: code review, architecture check, quality, gap analysis default: bkit:code-analyzer validate: bkit:design-validator gap: bkit:gap-detector qa: bkit:qa-strategist team: bkit:cto-lead.
gcp-cloud-logging
Google Cloud Logging — log search, VPC flow logs, firewall logs, audit logs, log buckets and views. Use when searching GCP logs, investigating denied VPC flow traffic, checking who deleted a VM, analyzing firewall rule hits, or troubleshooting a GCP application error.
dead-code-cleanup
Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size, or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when discussing technical debt, code hygiene, or repository maintenance.
laravel-audit-performance
Audit a Laravel application's performance deeply and safely: unnecessary queries, N+1, collection vs database work, memory amplification, repeated computation, I/O, queues, and rendering cost — verifying that every proposed optimization preserves behavior before reporting it. Use when auditing performance or…
roundtrip-radar
Per-journey code audit tracing data through complete user flows for bugs, data safety, performance, and round-trip completeness. Discovers workflows, audits each end-to-end, rolls up cross-cutting issues, and supports natural-language flow tracing. Triggers: "roundtrip audit", "trace user journey", "/roundtrip-radar".
time-bomb-radar
Finds deferred operations that crash on aged data -- code that passes every test but breaks weeks or months after release. Covers cascade deletes, cache expiry, trial paths, background accumulation, date-threshold transitions, and scheduled side effects. Triggers: "time bomb", "time-bomb", "/time-bomb-radar", "aged…