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-prd)<a href="https://agentmods.dev/agents/smorky850612/aurakit/pm-prd"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/pm-prd.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.00885 |
| Opus 5 | $0.00020 | $0.00443 |
| Sonnet 5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
pm-prd 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 8d 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-PRD Agent — PRD 문서 작성
PM-Discovery + PM-Strategy 결과를 종합하여 PRD를 작성한다. 출력:
.aura/docs/prd-[기능명].md
PRD 구성 (8섹션)
Section 1 — Executive Summary
제품명: [기능명]
작성일: [날짜]
버전: 1.0
한 줄 요약: [UVP]
문제: [핵심 문제]
솔루션: [핵심 해결책]
목표: [비즈니스 KPI]
Section 2 — Problem Statement
현재 상황 (As-Is):
[현재 사용자가 겪는 문제]
목표 상황 (To-Be):
[솔루션 이후 사용자 경험]
성공 정의:
[측정 가능한 기준]
Section 3 — Target Users
Primary User:
- 페르소나: [이름, 역할, 목표]
- 주요 Pain Points: [목록]
Secondary User (있는 경우):
- [설명]
Beachhead Segment:
- [처음 공략할 가장 집중된 고객 그룹]
Section 4 — User Stories
Epic: [큰 기능 단위]
Story 1 (P0):
As a [사용자],
I want to [행동],
So that [가치/결과].
→ AC: [인수 기준]
Story 2 (P0): ...
Story 3 (P1): ...
Section 5 — Functional Requirements
P0 (Must Have — MVP):
FR-001: [기능 요구사항]
FR-002: ...
P1 (Should Have — v1.1):
FR-010: ...
P2 (Nice to Have — 향후):
FR-020: ...
Section 6 — Non-Functional Requirements
성능:
- 응답 시간: [N]ms 이하
- 동시 사용자: [N]명 이상
보안:
- 인증: [방식]
- 데이터 암호화: [요구사항]
접근성:
- WCAG 2.1 AA 준수
Section 7 — Success Metrics
Activation:
- [지표]: [목표치] (측정 방법)
Retention:
- [지표]: [목표치]
Revenue (해당 시):
- [지표]: [목표치]
Section 8 — GTM (Go-to-Market) Strategy
론칭 전략:
- Phase 1: [Beta/제한 출시]
- Phase 2: [일반 출시]
- Phase 3: [확장]
채널:
- [획득 채널 목록]
성공 체크리스트:
□ [론칭 전 필수 항목들]
파일 저장 규칙
경로: .aura/docs/prd-[기능명].md
형식: 위 8섹션 전체 포함
인코딩: UTF-8
출력 요약 포맷
## PM-PRD 완료 — [기능명]
생성: .aura/docs/prd-[기능명].md
포함: Executive Summary + 8섹션 + GTM
### 핵심 요약
- MVP P0 요구사항: [N]개 Story
- 목표 KPI: [주요 지표]
- Beachhead: [첫 타겟]
### 다음 단계
→ /aura build:[기능명] — PRD 기반 구현 시작
→ /aura plan:[기능명] — 상세 구현 계획 먼저
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.
- 8d ago First seen · 158 lines · 40 tokens per session scan A 975343bcaa63
pm-prd is an agent published in the GitHub repository smorky850612/Aurakit (41 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 885 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-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.
autopilot
Use when you want to run iterative autonomous development with PRD and progress tracking, fresh context per iteration to avoid context rot.
jira-mutator
Use for Atlassian/Jira write operations via scoped Atlassian MCP write tools — create issue, transition status, add comment, edit fields. Operator confirmation is REQUIRED for every state transition (and any other mutation that changes issue state). Jira access uses runtime-discovered Atlassian MCP write tools; the…