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 Adelie-Squad/solosquad --skill docsgit clone --depth 1 https://github.com/Adelie-Squad/solosquadWrote 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/adelie-squad/solosquad/docs)<a href="https://agentmods.dev/skills/adelie-squad/solosquad/docs"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/docs/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/adelie-squad/solosquad/docs"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/docs.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.00216 | $0.03097 |
| Opus 5.5 | $0.00086 | $0.01239 |
| Sonnet 5.5 | $0.00043 | $0.00619 |
| Haiku 4.5 | $0.00022 | $0.00310 |
Grade A, and why
docs 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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Manager Skill — v1.3.8 (문서 관리 단일 권위)
너는 기획 산출 문서의 대화형 큐레이션 매니저다. "이 문서 어디 둬?", "PRD 어느 버전으로?",
"배포 전에 뭐 갱신해?", "리포트 어디에 쌓아?" 류 질문에 아래 체계로 답하고 배치·생성·갱신을
안내한다. 역할 분리: docs=어디에·어떤 버전으로·언제 최신화·외부냐 내부냐 (cross-doc 큐레이션)
· prd=한 PRD 를 어떻게 쓰나 (per-PRD writer). 둘을 섞지 않는다.
작성 표준 (점진공개): 공통 표준은 skills/skill-core/primitive-core.md — 특히 §3.2(description
공식) · §3.3(정량 한도) · §5(rubric). 결정적 동작은 npm run docs-check 게이트로 위임하고,
파일 이동·삭제 등 파괴적 동작은 적용 전 항상 확인(검증 게이트 경유 — 직접 조작 금지).
스코프 = repository 단위 (load-bearing): docs·버전의 단위는 repo다. 각 repo 가 자기
package.json(version)·docs/·CHANGELOG·manual 을 갖고 독립적으로 x/y/z 를 올린다(또는 안 올린다).
PM 은 각 repo 를 기준으로 문서를 사고. 한 워크플로우가 여러 repo 를 건드려도 release 하는 repo 만
버전·PRD 가 따른다(작업≠배포).
1. 문서 1차 축 = 외부(사용자 대면) vs 내부(기획·개발 전용)
경계는 package.json.files 가 강제(load-bearing). 내부 문서는 npm 패키지로 새지 않고, 외부
문서는 배포 게이트로 최신화된다. 분류가 헷갈리면 "이게 npm 으로 배포돼 사용자가 보나?" 로 가른다.
| 축 | 타입 | 위치 | npm | 청자 |
|---|---|---|---|---|
| 🌐 외부 | readme | README.md / README.kr.md |
✅ 자동 | 잠재 사용자·기여자 |
| changelog | CHANGELOG.md |
✅ files | 사용자 | |
| manual † | manual/master-guide_{ko,en}.html, manual/*.md |
✅ files | 제품 사용자 | |
| 🔒 내부 | prd | docs/prd/v<N.N.N>_<name>.md |
✗ | 기획·개발(본인) |
| ideation | docs/ideation/<name>_<YYMMDD>.md |
✗ | 기획(발산) | |
| poc | docs/poc/<name>.{mjs,md} |
✗ | 개발(실증) | |
| policy | docs/policy/<topic>.md |
✗ | 개발(불변 계약) | |
| architecture | docs/architecture.md |
✗ | 개발(구조 living) | |
| roadmap | docs/roadmap.md |
✗* | 기획(비전 living) |
* roadmap 은 외부 공개 제품이면 package.json.files 옵트인(트리거는 사람이 결정).
† manual 은 제품 특성 조건부 — 코드/문서를 사용자가 보는 제품(agent·OSS·CLI; SoloSquad 해당)만.
일반 웹/모바일 앱은 생략 가능(게이트도 부재 시 스킵).
불변식: package.json.files 에 docs/ 가 들어가면 안 된다(내부 누출). docs-check 가 검사.
스코프 계층 (직교 축): 위 위치는 repo-relative. 타입은 두 계층 —
| 계층 | 타입 | 위치 |
|---|---|---|
| repo | prd · architecture · roadmap · poc · policy · README · CHANGELOG · manual | <repo>/docs/·루트 (release-bound, 버전 결합) |
| org | ideation · reports | <org>/docs/ 워크스페이스 (cross-repo 발산·근거, class A 무관) |
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.
- 1mo ago First seen · 165 lines · 216 tokens per session scan A 50e02ec5b704
docs is a skill published in the GitHub repository Adelie-Squad/solosquad (25 stars, last pushed 2d ago), licensed MIT. It adds 216 tokens to every session and 3,097 once invoked, about $0.0009 per session on Opus 5.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
architecture
This skill should be used when managing Architecture Decision Records or C4 diagrams.
soleur-archive-kb
This skill should be used when archiving completed knowledge-base artifacts (brainstorms, plans, specs) to their archive/ subdirectories with timestamp prefixes and git history preservation.
soleur-deploy-docs
This skill should be used when validating the documentation build and preparing for Cloudflare Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.
soleur-docs-site
This skill should be used when scaffolding a Markdown-based documentation site using Eleventy. It generates a complete docs setup with base layout, data files, GitHub Pages deployment workflow, and passthrough copy configuration.
soleur-incident
This skill should be used when scaffolding a redaction-gated post-incident report (PIR) after a production incident.
sync
Populate your company knowledge base from the existing codebase.