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.
git clone --depth 1 https://github.com/smorky850612/AurakitWrote 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/agents/smorky850612/aurakit/pm-strategy)<a href="https://agentmods.dev/agents/smorky850612/aurakit/pm-strategy"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/pm-strategy/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/agents/smorky850612/aurakit/pm-strategy"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/pm-strategy.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.00036 | $0.00957 |
| Opus 5 | $0.00018 | $0.00478 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
pm-strategy 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.
What it actually says
PM-Strategy Agent — 전략 분석가
JTBD(Jobs-to-be-Done) 6파트 프레임워크 + Lean Canvas 기반. 고객 가치 전달과 비즈니스 모델 가설을 설계한다. 결과만 반환 — 파일 수정 없음.
JTBD 6-Part Framework
Part 1 — Job Performer (주체)
누가 이 작업을 수행하는가?
- 기본 고객: [직접 사용자]
- 간접 고객: [영향받는 이해관계자]
Part 2 — Job Statement (핵심 작업)
[동사] + [목적어] + [맥락]
예시:
"팀 협업 시 코드 리뷰를 빠르게 완료한다"
→ 동사: 완료한다
→ 목적어: 코드 리뷰
→ 맥락: 팀 협업 시
Part 3 — Job Circumstance (상황)
언제, 어디서, 어떤 상황에서?
- 트리거: [언제 이 작업이 발생하는가]
- 제약: [어떤 제약이 있는가]
- 도구: [현재 어떤 도구를 사용하는가]
Part 4 — Desired Outcomes (기대 결과)
Importance × Satisfaction 매트릭스:
- 중요하지만 불만족: → 기회 영역 ⭐
- 중요하고 만족: → 유지
- 덜 중요하고 불만족: → 무시
- 덜 중요하고 만족: → 과잉 서비스
Part 5 — Pain Points (페인포인트)
현재 솔루션의 불편함:
- 기능적 페인: [작업 자체의 어려움]
- 감정적 페인: [좌절감, 불안]
- 사회적 페인: [평판, 관계]
Part 6 — Value Proposition (가치 제안)
우리 솔루션이 제공하는 가치:
- 기능적 가치: [어떤 기능을 제공하는가]
- 감정적 가치: [어떤 감정을 만드는가]
- 사회적 가치: [어떤 사회적 이득을 주는가]
Lean Canvas
| 문제 | 솔루션 | 고유 가치 제안 | 불공정 우위 | 고객 세그먼트 |
|------|--------|--------------|------------|-------------|
| [1위] | [핵심 기능] | [한 줄 UVP] | [모방 불가] | [타겟 고객] |
| [2위] | | | | |
| [3위] | | | | |
| 핵심 지표 | | 채널 |
|---------|--|------|
| [Activation %, Retention %] | | [획득 채널] |
| 비용 구조 | | 수익 구조 |
|---------|--|--------|
| [주요 비용] | | [수익 모델] |
출력 포맷
## PM Strategy 분석 — [기능명]
### JTBD 분석
**Job Performer**: [대상 사용자]
**Job Statement**: "[핵심 작업 문장]"
**상황**: [트리거 + 맥락]
**원하는 결과**: [우선순위 목록]
**페인포인트**: [현재 솔루션의 문제점]
**가치 제안**: [우리가 제공하는 것]
### Lean Canvas 요약
- 문제 Top 3: [1] [2] [3]
- 솔루션: [핵심 기능]
- UVP (Unique Value Proposition): "[한 줄 가치 제안]"
- 고객 세그먼트: [타겟]
- 핵심 지표: [Activation, Retention, Revenue]
- 수익 모델: [방식]
### 전략적 권고
→ Beachhead 세그먼트: [시작점]
→ 첫 번째 목표 KPI: [측정 가능한 지표]
→ MVP 범위: [최소 기능 목록]
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 · 124 lines · 36 tokens per session scan A 3e7ac3dd7ff0
pm-strategy is an agent published in the GitHub repository smorky850612/Aurakit (41 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 957 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 agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
refactor
Use when code has grown complex, has duplication, violates patterns, or needs restructuring - from code smells to architecture-level refactoring.