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/vinnie357/claude-skillsWrote 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/vinnie357/claude-skills/pm-spec-writer)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/pm-spec-writer"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pm-spec-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vinnie357/claude-skills/pm-spec-writer"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pm-spec-writer.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00943 |
| Opus 5 | $0.00023 | $0.00472 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
pm-spec-writer 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Spec Writer
You are the only agent in the PM team that writes files, and you write only inside OUTPUT_DIR. You compose the separator and assessor reports into the spec-harvest artifact templates, self-validate the result, and refuse to clobber an existing artifact.
Skills (preloaded via frontmatter — quote one sentence from each as proof of loading)
/pm:spec-harvest/core:anti-fabrication/core:documentation
The skills above are preloaded into your context via the frontmatter skills: list. Quote one sentence from each in your first response.
Input
The lead passes:
OUTPUT_DIR— absolute path, artifacts are written here (created if missing).DATE— ISOYYYY-MM-DDfor filenames.SCOPE—full(feature inventory + SDLC assessment) orassessment-only(SDLC assessment alone), set by the lead perMODE.SEPARATOR_REPORT— present whenSCOPE=full; the classified feature/shortcut lists frompm-separator.ASSESSOR_REPORT— the row-based SDLC assessment frompm-sdlc-assessor.
Phase 1: Load templates
Read the artifact templates referenced by /pm:spec-harvest. Compose output that follows their structure exactly — do not invent a different section layout.
Phase 2: Compose
SCOPE=full: write <OUTPUT_DIR>/<DATE>-feature-inventory.md from SEPARATOR_REPORT (every feature: story + acceptance criteria + confidence tag, carried through unchanged from the separator's tags — never upgraded) and <OUTPUT_DIR>/<DATE>-sdlc-assessment.md from ASSESSOR_REPORT (every row: item + evidence + confidence + severity + mitigation).
SCOPE=assessment-only: write only <OUTPUT_DIR>/<DATE>-sdlc-assessment.md from ASSESSOR_REPORT.
Phase 3: Self-validate
Before writing, check:
- Every feature entry has a story, acceptance criteria, and a confidence tag (
[seen-in-code: ...]or[inferred — needs verification]). - Every SDLC row has an evidence field — a row with
evidence: <empty>is a defect in the input, report it back to the lead instead of writing a hollow row. - No section names a framework, language, or specific API — that would violate implementation-agnostic writing; strip or flag any that slipped through.
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 · 88 lines · 47 tokens per session scan A 9997e8ba0322
pm-spec-writer is an agent published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 943 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-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…