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 skills add eigent-ai/agent-skills --skill pm-skillsgit clone --depth 1 https://github.com/eigent-ai/agent-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/skills/eigent-ai/agent-skills/pm-skills)<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/pm-skills"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/pm-skills/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/skills/eigent-ai/agent-skills/pm-skills"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/pm-skills.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.00072 | $0.01107 |
| Opus 5 | $0.00036 | $0.00553 |
| Sonnet 5 | $0.00014 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
pm-skills 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 10d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
65 skills and 36 chained workflows covering the full PM work lifecycle. The three core skills below cover the most common PM artifacts: requirements, goal-setting, and meeting capture. Each produces a structured, shareable output ready to hand off to stakeholders or a team.
Source Repository
- GitHub: phuryn/pm-skills
- Install upstream:
npx skills add phuryn/pm-skills
/write-prd
Drafts a full product requirements document from a brief description. Includes problem statement, user stories, assumptions, edge cases, acceptance criteria, and open questions.
Workflow
- Gather: feature name, the problem it solves, primary users, and any known constraints.
- Write the problem statement — one paragraph, no solution language yet.
- Draft user stories: "As a [role], I want [action] so that [outcome]." Cover the primary flow and at least 2 edge cases.
- List assumptions (what must be true for this to work) and open questions (what needs a decision).
- Write acceptance criteria for each user story — specific, testable, binary pass/fail.
- Return the full PRD in a structured format ready to paste into Notion, Confluence, or a doc.
Example prompts
| Use case | Task prompt |
|---|---|
| New feature | Write a PRD for a notification preferences center. Users need granular control over email, push, and in-app alerts by category. Include edge cases for users on multiple devices. |
| Internal tool | Write a PRD for an internal expense reporting tool. Finance team needs to approve, reject, and request more info. Current process is email-based and takes 2 weeks. |
| API product | Write a PRD for a public API rate limiting dashboard. Developers need to monitor usage, set alerts, and upgrade their plan without contacting sales. |
/plan-okrs
Generates a full OKR set from a goal or initiative — key results with measurable targets, leading indicators, and a tracking cadence. Also reviews existing OKRs for clarity and measurability.
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.
- 10d ago First seen · 85 lines · 0 tokens per session scan A 2fd4494ecb7c
pm-skills is a skill published in the GitHub repository eigent-ai/agent-skills (19 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,107 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.