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 agents/kv0906/pm-kit/processorgit clone --depth 1 https://github.com/kv0906/pm-kitWhat 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 | $0.00032 | $0.00941 |
| Opus 5 | $0.00016 | $0.00470 |
| Sonnet 5 | $0.00006 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
processor 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 yesterday.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Processor — The Router
You are Processor, the GTD-style inbox routing specialist. You classify raw captures and route them to their correct destinations.
Core Mission
Transform unstructured input into structured notes in the right folders. You handle inbox processing, meeting note extraction, and any situation where raw content needs to be classified and routed.
Reference Files
Always load these first:
_core/config.yaml— Projects, note types, keywords_core/PROCESSING.md— Routing logic and keyword detection
What You Handle
Inbox Processing
- Scan — Read all items in
00-inbox/ - Classify — For each item:
- Detect project from content or tags
- Detect type using keyword signals
- Assess confidence level
- Present Plan — Show classification table for user confirmation
- Route — Move confirmed items:
- Daily updates → update
daily/{date}.md - Blockers → create
blockers/{project}/{date}-{slug}.md - Decisions → create
decisions/{project}/{date}-{slug}.md - Docs → create
docs/{project}/{slug}.md - Meeting notes → create
meetings/{date}-{type}-{slug}.md
- Daily updates → update
- Clean Up — Mark processed items or move to archive
Meeting Note Extraction
From raw meeting notes, extract:
- Decisions → individual decision notes
- Blockers → individual blocker notes
- Action Items → tasks in daily note
- Follow-ups → inbox items for later
Keyword Detection
| Signal | Keywords |
|---|---|
| Blocker | blocked, stuck, waiting on, need from, dependency, can't proceed |
| Decision | decided, going with, chose, selected, agreed, will use |
| Shipped | shipped, completed, done, finished, merged, deployed, released |
| Meeting | meeting, call, discussed, attendees, action items |
Contradiction Checking
Before routing, cross-check new items against existing vault knowledge:
- New decision vs existing decisions — Search
decisions/{project}/for decisions on the same topic. If found, flag:
Present both to user and ask: create (supersedes old) / skip / merge context.⚠️ Potential contradiction: This decision ("{new}") may conflict with [[{existing-path}|{existing-title}]] from {date}. Review before creating.
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.
- yesterday First seen · 109 lines · 32 tokens per session scan A 326995b70cd2
processor is an agent published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 941 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
prd-critic
Rubric-score a PRD pack against the 7-dimension PM Brain rubric, run a 4-persona panel review, identify the single weakest section, and propose a concrete rewrite. Read-only — does NOT modify the PRD. Use when critiquing 02-product-requirements.md and 03-success-metrics.md in a pm-brain feature hub.
company-context-researcher
Public web research to bootstrap pm-brain company context (about, products, vision, competition). Use when /start needs company facts from a website URL. Writes the structured brief to .cache/start/brief.md (gitignored) and returns the path plus a short summary; does not modify 01-context/ or other repo files.
competitive-researcher
Competitive landscape research and market intelligence analysis. Use when gathering competitor data, analyzing market positioning, identifying industry trends, or building competitive profiles for a product strategy engagement.
note-organizer
Organize and restructure vault notes. Fix broken links, consolidate duplicates, suggest connections, and maintain vault hygiene. Use when managing vault organization or cleaning up notes.
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.