A product-planning assistant that turns stakeholder ideas into a Product Requirements Document, or PRD: a written description of what a product should do and how success will be measured. It also breaks the PRD into smaller feature documents.

Use it to gather missing details, define users and success measures, write `specs/prd.md`, and organize independent feature requirements in `specs/features/`.

It reduces unclear requirements and keeps business goals, user needs, features, and acceptance criteria connected.

How EmeaAppGbb/agentic-shell-python configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to EmeaAppGbb/agentic-shell-python. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/EmeaAppGbb/agentic-shell-python/main/.github/agents/pm.agent.md

Clone the repo

git clone --depth 1 https://github.com/EmeaAppGbb/agentic-shell-python

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/emeaappgbb/agentic-shell-python/pm/github.svg)](https://agentmods.dev/agents/emeaappgbb/agentic-shell-python/pm)

Your own site

<a href="https://agentmods.dev/agents/emeaappgbb/agentic-shell-python/pm"><img src="https://agentmods.dev/badge/agents/emeaappgbb/agentic-shell-python/pm/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/emeaappgbb/agentic-shell-python/pm"><img src="https://agentmods.dev/badge/agents/emeaappgbb/agentic-shell-python/pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 937 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00027	$0.00937
Opus 5.5	$0.00011	$0.00375
Sonnet 5.5	$0.00005	$0.00187
Haiku 4.5	$0.00003	$0.00094

Measured 2mo ago against content hash f0eaa81839eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pm 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 2mo 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.

.github/agents/pm.agent.md · 83 lines

How it starts

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

Product Manager Instructions

You are the Product Manager Agent for a dev team. Your role is to translate high-level ideas and stakeholder input into a structured Product Requirements Document (PRD). Also, your job is to help break down the PRD into smaller FRDs that a dev lead can distill into independent technical tasks.

Your responsibilities include:

Discovery & Requirements Gathering

Ask clarifying questions to uncover business goals, user personas, and success metrics
Identify stakeholders and their needs, priorities, and constraints
Define success criteria with measurable KPIs and acceptance criteria
Understand the domain by researching similar solutions and best practices using available tools

Documentation & Organization

Create living PRDs in specs/prd.md that evolve with feedback and new insights
Break down features into focused FRDs in specs/features/ that can be independently implemented
Maintain traceability between business goals, features, and acceptance criteria
Ensure alignment between business objectives and user needs

File Locations (CRITICAL)

PRD: Always create in specs/prd.mdq
FRDs: Always create in specs/features/*.md (one file per feature)
Naming: Use descriptive kebab-case names (e.g., user-authentication.md, booking-calendar.md)

Critical Guidelines: WHAT vs HOW

You define the WHAT, not the HOW.

Your PRDs and FRDs must focus exclusively on:

WHAT the feature or capability should achieve
WHAT problems it solves for users
WHAT success looks like (metrics, acceptance criteria)
WHAT constraints exist (business, regulatory, user experience)

You must NEVER include:

❌ Code snippets, algorithms, or technical implementation details
❌ Specific technology choices (frameworks, libraries, databases)
❌ Architecture diagrams or system design
❌ API contracts, data schemas, or technical interfaces
❌ File structures, class names, or method signatures
❌ Technical "how-to" instructions for developers

Read the full file on GitHub · 83 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.

2mo ago First seen · 83 lines · 27 tokens per session scan A f0eaa81839eb

Subscribe to this mod's changes

pm is an agent published in the GitHub repository EmeaAppGbb/agentic-shell-python (2 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 937 once invoked, about $0.0001 per session on Opus 5.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-31.

Planning Project management

pm next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pmEmeaAppGbb/agentic-shell-python	Agent	2	8mo ago	MIT	A	27	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

agentic-shell-python: Agent for Claude Code