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 SW-in-beta/simon-skills --skill simon-pmgit clone --depth 1 https://github.com/SW-in-beta/simon-skillsWrote 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/sw-in-beta/simon-skills/simon-pm)<a href="https://agentmods.dev/skills/sw-in-beta/simon-skills/simon-pm"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-pm/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/sw-in-beta/simon-skills/simon-pm"><img src="https://agentmods.dev/badge/skills/sw-in-beta/simon-skills/simon-pm.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.00145 | $0.04902 |
| Opus 5 | $0.00072 | $0.02451 |
| Sonnet 5 | $0.00029 | $0.00980 |
| Haiku 4.5 | $0.00015 | $0.00490 |
Grade A, and why
simon-pm 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simon-pm
프로젝트 매니저 스킬. 사용자와 인터뷰하며 PRD를 작성하고, 작업을 분해하여 simon/simon-grind에게 분배한 뒤, 전체 프로젝트 완성까지 관리합니다.
Progressive Disclosure: 각 Phase의 참조 파일은 해당 Phase 진입 시점에만 로딩한다. 모든 참조 파일을 한꺼번에 읽지 않는다 — 컨텍스트 윈도우를 절약하고 현재 Phase에 집중하기 위함이다.
Scope Guard
이 스킬은 여러 기능을 조율하는 전체 프로젝트 관리를 위한 것입니다. 소규모 작업에 PM 워크플로를 적용하면 오버헤드만 늘어나므로, 아래 기준으로 적용 여부를 먼저 판단합니다:
| 기준 | simon-pm 적용 | simon-dev로 리다이렉트 |
|---|---|---|
| 기능(Feature) 수 | 3개 이상 | 1-2개 |
| 예상 변경 파일 수 | 15개 이상 | 15개 미만 |
| 기능 간 의존성 | 있음 | 없음 |
| PRD/작업 분해 필요 | 필요 | 불필요 (범위가 이미 명확) |
리다이렉트 시 행동: 사용자에게 왜 simon-pm이 과한지 간략히 설명하고, simon-dev 사용을 제안한다. 강제하지 말고 사용자가 그래도 PM 워크플로를 원하면 진행한다.
Instructions
이 스킬은 7단계 파이프라인으로 동작합니다:
| Phase | 이름 | 핵심 | 참조 파일 |
|---|---|---|---|
| 0 | Project Setup | 프로젝트 유형 판별, 실행 모드 선택 | project-setup.md |
| 1 | Spec-Driven Design | 인터뷰 → Spec(WHAT) → Architecture(HOW) → PRD | spec-driven-design.md, spec-template.md, technical-architecture.md |
| 2 | Task Breakdown | PRD → 기능 분해 → 의존성 그래프 → 실행 계획 | task-breakdown.md |
| 3 | Environment Setup | 프로젝트 뼈대, 의존성, 설정 | environment-setup.md |
| 4 | Feature Execution | simon-dev/simon-grind 파이프라인으로 기능별 구현 + 진행 관리 | feature-execution.md |
| 5 | Full Verification | 전체 레벨 통합 검증 | full-verification.md |
| 6 | Delivery | 최종 보고, 가이드 리뷰, PR 생성 | delivery.md |
Reference Loading Policy: 각 Phase 진입 시 해당 행의 "참조 파일"만 읽는다. 이전/이후 Phase의 참조 파일은 로딩하지 않는다.
Dependencies: simon/simon-grind 스킬을 활용합니다. Claude Code의 Agent 및 Agent Teams 기능을 사용합니다.
Cross-Cutting Protocols
Shared Protocols:
~/.claude/skills/_shared/preamble.md읽기 — Session Isolation, Error Resilience, Forbidden Rules, Agent Teams, Cognitive Independence 공통 프로토콜 포함.
What ships with it
9 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.
- references/delivery.md 1.8 KB
- references/environment-setup.md 1.9 KB
- references/feature-execution.md 14 KB
- references/full-verification.md 4.9 KB
- references/project-setup.md 1.0 KB
- references/spec-driven-design.md 5.5 KB
- references/spec-template.md 3.8 KB
- references/task-breakdown.md 4.3 KB
- references/technical-architecture.md 6.0 KB
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 · 316 lines · 145 tokens per session scan A 49dc9acc5b20
simon-pm is a skill published in the GitHub repository SW-in-beta/simon-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session and 4,902 once invoked, about $0.0007 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.