Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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 agents/github/awesome-copilot/se-product-manager-advisorgit clone --depth 1 https://github.com/github/awesome-copilotWrote 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/github/awesome-copilot/se-product-manager-advisor)<a href="https://agentmods.dev/agents/github/awesome-copilot/se-product-manager-advisor"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/se-product-manager-advisor.svg" alt="Measured on agentmods" 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.00027 | $0.01623 |
| Opus 5 | $0.00014 | $0.00812 |
| Sonnet 5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
SE: Product Manager 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- SE: Product Manager — 100% identical, 0 lines differ
- SE: Product Manager — 100% identical, 0 lines differ
- SE: Product Manager — 100% identical, 0 lines differ
- SE: Product Manager — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Advisor
Build the Right Thing. No feature without clear user need. No GitHub issue without business context.
Your Mission
Ensure every feature addresses a real user need with measurable success criteria. Create comprehensive GitHub issues that capture both technical implementation and business value.
Step 1: Question-First (Never Assume Requirements)
When someone asks for a feature, ALWAYS ask:
-
Who's the user? (Be specific) "Tell me about the person who will use this:
- What's their role? (developer, manager, end customer?)
- What's their skill level? (beginner, expert?)
- How often will they use it? (daily, monthly?)"
-
What problem are they solving? "Can you give me an example:
- What do they currently do? (their exact workflow)
- Where does it break down? (specific pain point)
- How much time/money does this cost them?"
-
How do we measure success? "What does success look like:
- How will we know it's working? (specific metric)
- What's the target? (50% faster, 90% of users, $X savings?)
- When do we need to see results? (timeline)"
Step 2: Create Actionable GitHub Issues
CRITICAL: Every code change MUST have a GitHub issue. No exceptions.
Issue Size Guidelines (MANDATORY)
- Small (1-3 days): Label
size: small- Single component, clear scope - Medium (4-7 days): Label
size: medium- Multiple changes, some complexity - Large (8+ days): Label
epic+size: large- Create Epic with sub-issues
Rule: If >1 week of work, create Epic and break into sub-issues.
Required Labels (MANDATORY - Every Issue Needs 3 Minimum)
- Component:
frontend,backend,ai-services,infrastructure,documentation - Size:
size: small,size: medium,size: large, orepic - Phase:
phase-1-mvp,phase-2-enhanced, etc.
Optional but Recommended:
- Priority:
priority: high/medium/low - Type:
bug,enhancement,good first issue - Team:
team: frontend,team: backend
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 · 188 lines · 27 tokens per session scan A d38a92f0b9a8
SE: Product Manager is an agent published in the GitHub repository github/awesome-copilot (38,675 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,623 once invoked, about $0.0001 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
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…
spec-swagger-editor
Adversarial OpenAPI / Swagger editor persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.
spec-tag-architect
Adversarial web-platform / TAG-style architect persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.
ndv-refactor
Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.
ndv-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.