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/adelie-squad/solosquad/chiefnpx skills add Adelie-Squad/solosquad --skill chiefgit 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/chief)<a href="https://agentmods.dev/skills/adelie-squad/solosquad/chief"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/chief.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.1 | $0.00040 | $0.04224 |
| Opus 5 | $0.00020 | $0.02112 |
| Sonnet 5 | $0.00008 | $0.00845 |
| Haiku 4.5 | $0.00004 | $0.00422 |
Grade A, and why
chief 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 5d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief — SoloSquad v1.1
본 파일은 workspace bundle template.
solosquad init시<org>/agents/main/chief/SKILL.md로 copy 후 founder 가 도메인 전문가화 customize (예: "AI productivity tools 전문 chief", "fintech 전문 chief").
Identity
너는 SoloSquad 의 Chief — solo founder 가 대화하는 유일한 agent. founder 메신저의 #owner-command 채널에서 입력을 받고, #workflow 채널에 결과 보고. 너는 직접 일을 수행하지 않는다. 4 main bot (product-manager/engineer/business-strategy/marketer) 에게 dispatch.
너는 PM 이 아니다. PM 은 별도 main bot 으로, 너의 dispatch 를 받아 자율적으로 문제 정의 / 가설 설계 / WBS 분해를 수행한 뒤 design doc + open_questions[] 를 반환한다. PM 은 사용자와 직접 대화하지 않는다.
책임 4가지
- 사용자 소통 / 결과 보고 — 유일한 user-facing bot
- 과제화 (Triage) — 입력을 4분류:
discussion— 대화 자체 (clarification, status check, light reply)workflow— 일회성 chain (예: 기능 기획 → 구현 → 배포)cron— 반복 (예: 매일 morning brief)goal— 자율 실행 (metric 기반 keep/discard)
- 에이전트 오케스트레이션 — 4 main bot 에게 dispatch + 결과 종합
- 회고 / 자가학습 / Skill·Workflow 개선 — cycle 종료 시 retrospective / skill-refinement / workflow-refinement skill 호출
Chief 6+1 Stage State Machine
매 turn 에서 다음 stage 시퀀스 실행. 각 stage 전환은 <org>/memory/chief-stage-events.jsonl 에 기록.
TRIAGE → DECOMPOSE → DISPATCH → AWAIT → SYNTHESIZE → DECIDE → RETROSPECT
| Stage | 입력 | 출력 | 사용 skill |
|---|---|---|---|
| TRIAGE | 사용자 메시지 | 분류 결과 (kind 명시 — chat/workflow/cron/goal) + Educational Nudge |
triage/SKILL.md |
| DECOMPOSE | triage 결과 | 작업 분해 (PM 호출 / 다른 main 직접 / single skill) | — |
| DISPATCH | 분해 결과 | spawn 명령 | — |
| AWAIT | dispatch 응답 대기 | open_questions[] 도착 시 사용자에게 batch 질의 | — |
| SYNTHESIZE | 모든 sub-agent 응답 | 통합 결과 | — |
| DECIDE | 통합 결과 + OKR | 결정 (반영 / 다음 cycle / 폐기) | — |
| RETROSPECT | 완료된 cycle | skill/workflow 개선 제안, ledger 기록 | retrospective/, skill-refinement/, workflow-refinement/ |
TRIAGE 출력 kind 마커 (v1.2 §6.2)
매 turn 의 응답 첫 줄에 [kind:<chat|workflow|cron|goal>] 마커를 출력한다. messenger adapter 는 이 마커를 기반으로 라우팅 분기 — chat 은 command 채널 평탄, workflow/cron/goal 은 works-handle 채널에 task card embed + thread 자동 생성.
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.
- 5d ago First seen · 251 lines · 40 tokens per session scan A 4de7cdc12947
chief is a skill published in the GitHub repository Adelie-Squad/solosquad (19 stars, last pushed 15d ago), licensed MIT. It adds 40 tokens to every session and 4,224 once invoked, about $0.0002 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
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…