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 skills/kv0906/pm-kit/linearnpx skills add kv0906/pm-kit --skill lineargit 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.00096 | $0.01906 |
| Opus 5 | $0.00048 | $0.00953 |
| Sonnet 5 | $0.00019 | $0.00381 |
| Haiku 4.5 | $0.00010 | $0.00191 |
Grade A, and why
linear 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.
How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/linear — Linear Integration
Bridge your PM-Kit vault with Linear issue tracking. Search, create, sync issues and link them to vault notes.
Context
Today's date: !date +%Y-%m-%d
Config: @_core/config.yaml
Active projects: !ls 01-index/*.md 2>/dev/null | sed 's|01-index/||;s|\.md||'
Input
User input: $ARGUMENTS
Sub-commands
Parse the first word of $ARGUMENTS to determine the sub-command:
| Input starts with | Sub-command | Purpose |
|---|---|---|
setup |
Setup | Guide MCP connection + auth |
sync |
Sync | Pull recent updates into vault |
create |
Create | Create Linear issue from vault context |
search or a question |
Search | Find Linear issues |
link |
Link | Connect vault note ↔ Linear issue |
| (empty) | Status | Show connection status + recent activity |
Step 0: Connection Check
Before any sub-command (except setup), verify Linear MCP is available:
- Try calling any Linear MCP tool (e.g., list viewer's issues with a small limit)
- If the tool call fails or
mcp__linear-server__*tools are not available:
Linear MCP is not connected yet.
Run `/linear setup` to connect — it takes about 30 seconds.
Then stop. Don't attempt other operations without a working connection.
setup — Connect Linear MCP
Guide the user through connecting Linear's remote MCP server to Claude Code.
Steps to present to user:
## Linear MCP Setup
Linear's MCP server is hosted by Linear — no local install needed.
### Step 1: Add the server
Run this in your terminal:
claude mcp add --transport http linear-server https://mcp.linear.app/mcp
### Step 2: Authenticate
In a Claude Code session, run:
/mcp
Then follow the OAuth flow — it'll open your browser to authorize Linear access.
### Step 3: Verify
Once authenticated, try:
/linear
You should see your recent Linear activity.
After presenting, ask if the user wants help running these commands now.
If the user confirms, run the claude mcp add command via Bash, then inform them they need to run /mcp themselves (it requires interactive browser auth that can't be automated).
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 · 262 lines · 96 tokens per session scan A 20c04a3f3a86
linear is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 1,906 once invoked, about $0.0005 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 skills, from other repositories
critique-prd
Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.
critique-agent
Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.
interview-frameworks
Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…
query-datasets
Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…
create-prd
Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.
create-internal-feature-announcement
Drafts an internal feature announcement (IFA) from the PRD pack and user sources using the repo template, then writes 04-internal-feature-announcement.md. Use when: IFA, internal feature announcement, internal FAQ, Slack IFA prep, launch comms pack, or internal product documentation from the template.