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 commands/studiokjm/ai-harness-template/pmgit clone --depth 1 https://github.com/studioKjm/ai-harness-templateWrote 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/commands/studiokjm/ai-harness-template/pm)<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/pm"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/pm.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.00032 | $0.00496 |
| Opus 5 | $0.00016 | $0.00248 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
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 6d 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 Generator
인터뷰 결과를 PRD(Product Requirements Document)로 변환한다
Instructions
Read the latest interview from .harness/ouroboros/interviews/ and generate a PRD.
PRD Structure
# PRD: {Project/Feature Name}
## Overview
- **Date**: YYYY-MM-DD
- **Author**: {from interview}
- **Status**: Draft
- **Source**: Interview {ref}
## Problem Statement
{What problem are we solving? Why does it matter?}
## Goals
### Must Have (P0)
- {goal from constraints.must}
### Should Have (P1)
- {goal from constraints.should}
### Nice to Have (P2)
- {from scope.future}
## Non-Goals
- {from goal.non_goals}
## User Stories
- As a {actor}, I want to {action} so that {benefit}
## Technical Requirements
### Architecture
{From ontology and tech_decisions}
### Data Model
{From ontology.entities — formatted as table}
| Entity | Fields | Relationships |
|--------|--------|---------------|
| {name} | {fields} | {relations} |
### API / Interface
{From ontology.actions}
### Constraints
- MUST: {constraints.must}
- MUST NOT: {constraints.must_not}
## Acceptance Criteria
{From seed AC, formatted as checklist}
- [ ] AC-001: {description}
- [ ] AC-002: {description}
## Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| {from interview assumptions_surfaced} | {H/M/L} | {mitigation} |
## Timeline
- MVP: {scope.mvp items}
- Future: {scope.future items}
Output
Save to docs/PRD-{name}-{date}.md and display summary:
PRD generated: docs/PRD-{name}-{date}.md
Summary:
P0 Goals: {count}
P1 Goals: {count}
User Stories: {count}
Acceptance Criteria: {count}
Risks: {count}
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.
- 6d ago First seen · 90 lines · 32 tokens per session scan A 593a0cd9d73b
pm is a command published in the GitHub repository studioKjm/ai-harness-template (43 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 496 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 commands, from other repositories
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
VibeGuard: Live Truth
Verify live claims with fresh facts, inferences, and unresolved gaps.
capture-feedback
Quick feedback capture with structured signals.
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.