What is pm-kit AGENTS.md?

A repository guide for PM-Kit, a markdown-based workspace template that uses documents, templates, and shell scripts. It explains the project layout, setup commands, development tips, and testing instructions.

Use it when working on PM-Kit documentation, templates, configuration, setup or update scripts, agent files, and tests.

It gives a coding agent the project context needed to change PM-Kit safely. This reduces time spent searching for files and helps preserve the project’s documented guardrails.

pm-kit AGENTS.md — Instructions file by kv0906

Install

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.

agentmods

npx agentmods add instructions/kv0906/pm-kit/agents-md

Clone the repo

git clone --depth 1 https://github.com/kv0906/pm-kit

Made for: Codex, OpenCode.

Per session 697 This file is loaded in full into every session.

When invoked 697 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00697	$0.00697
Opus 5	$0.00349	$0.00349
Sonnet 5	$0.00139	$0.00139
Haiku 4.5	$0.00070	$0.00070

Measured 2d ago against content hash 0b5f545fea0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pm-kit AGENTS.md 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 2d 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.

AGENTS.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Audience: PM-Kit users/operators.

Project snapshot

PM-Kit is a markdown-first workspace template. Most work is in docs, templates, and shell scripts rather than compiled code.

Key paths:

Framework docs: README.md, CLAUDE.md, START_HERE.md, CHANGELOG.md
Runtime/config: _core/ (including _core/config.yaml)
Reusable templates: _templates/
Agent assets: .claude/ (agents/, skills/, rules/, hooks/)
Distribution metadata: .claude-plugin/plugin.json
Automation scripts: scripts/setup.sh, scripts/update.sh
Reference material: handbook/, examples/

Dev environment tips

Use rg/rg --files for fast discovery instead of manual folder scanning.
Use ./scripts/setup.sh after cloning to initialize or validate a local PM-Kit vault.
Before changing automation, read the script you are touching end-to-end and keep guardrails intact.
Keep edits repository-relative and avoid machine-specific absolute paths in docs and scripts.
If a change affects user-facing flow, update both docs and templates in the same PR.

Core commands

./scripts/setup.sh: initialize or verify local PM-Kit setup.
./scripts/update.sh --check: detect whether upstream framework updates are available.
./scripts/update.sh --dry-run: preview update effects without mutating files.
./scripts/update.sh: apply framework updates.
git status && git diff: required local sanity check before commit/PR.

Testing instructions

Inspect CI definitions in .github/workflows/ before significant changes.
Primary CI checks include:
- PR Changelog Check (.github/workflows/pr-changelog-check.yml)
- PR Auto Labeler (.github/workflows/pr-labeler.yml)
- Changelog On Merge (.github/workflows/changelog-on-merge.yml)
For script changes, test both:
- happy path
- guardrails (dirty git tree, missing prerequisites, invalid inputs)
For docs/template changes, verify command examples and paths still resolve.
Treat changes as incomplete until affected flows can be executed without manual patch-ups.

Read the full file on GitHub · 63 lines

Changes

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.

2d ago First seen · 63 lines · 697 tokens per session scan A 0b5f545fea0a

Subscribe to this mod's changes

pm-kit AGENTS.md is an instructions file published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 697 tokens to every session, about $0.0035 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.

claude-code obsidian product productmanagement productmanager

pm-kit AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

AGENTS.md

Project snapshot

Dev environment tips

Core commands

Testing instructions

What this file has done since we first saw it

Other instructions, from other repositories

pm-brain-for-cursor AGENTS.md

plannotator AGENTS.md

llm-wiki-agent GEMINI.md

textbook-to-note CLAUDE.md

vault-cortex AGENTS.md

ariadne AGENTS.md