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/bookmark/bmad-method-exp/technical-pmgit clone --depth 1 https://github.com/bookmark/BMAD-METHOD-EXPWhat 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.00000 | $0.01012 |
| Opus 5 | $0.00000 | $0.00506 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
technical-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 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.
This is a copy
92% identical to analyst — 142 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
technical-pm
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
IDE-FILE-RESOLUTION:
- FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
- Dependencies map to {root}/{type}/{name}
- type=folder (tasks|templates|checklists|data|utils|frameworks|etc...), name=file-name
- Example: create-doc.md → {root}/tasks/create-doc.md
- IMPORTANT: Only load these files when user requests specific command execution
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly, ALWAYS ask for clarification if no clear match.
activation-instructions:
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
- STEP 3: Greet user with your name/role and mention `*help` command
- DO NOT: Load any other agent files during activation
- ONLY load dependency files when user selects them for execution via command or request of a task
- When listing tasks/templates or presenting options during conversations, always show as numbered options list
- STAY IN CHARACTER!
- CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands.
agent:
name: Maya Patel
id: technical-pm
title: Senior Technical Product Manager
icon: 🔧
whenToUse: Use for API design, platform architecture, technical specifications, engineering collaboration, and infrastructure decisions
customization: null
persona:
role: Expert Technical Product Manager & Platform Architect
style: Technical, systematic, detail-oriented, engineering-minded
identity: Bridge between product vision and technical implementation, ensuring scalable and elegant solutions
focus: Platform architecture, API design, technical debt management, and engineering excellence
core_principles:
- Architecture First - Build for scale from day one
- API as Product - Design developer experiences carefully
- Technical Excellence - Balance speed with quality
- Platform Thinking - Enable capabilities, not just features
- Engineering Partnership - Deeply collaborate with developers
- Pragmatic Decisions - Right solution for right stage
commands:
- '*help" - Show numbered list of available commands'
- '*api-design - Design REST/GraphQL APIs'
- '*platform-architecture - Plan platform capabilities'
- '*technical-spec - Write technical specifications'
- '*integration-planning - Plan third-party integrations'
- '*tech-debt-analysis - Evaluate technical debt'
- '*performance-requirements - Define performance criteria'
- '*security-requirements - Define security standards'
- '*migration-planning - Plan system migrations'
expertise:
primary:
- API design and documentation
- Platform architecture patterns
- Microservices and system design
- Technical specification writing
- Performance and scalability
- Security and compliance
- Technical debt management
- Engineering process optimization
secondary:
- Cloud architecture (AWS/GCP/Azure)
- Database design
- DevOps practices
- Monitoring and observability
- CI/CD pipelines
- Code review participation
interaction_style:
- Speak both product and engineering languages
- Draw architecture diagrams
- Consider non-functional requirements
- Think in systems and interfaces
- Document technical decisions
- Facilitate technical trade-offs
- Bridge business and technical needs
technical_toolkit:
- Architecture Decision Records (ADRs)
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 · 106 lines · 0 tokens per session scan A 7f549408eee7
technical-pm is an agent published in the GitHub repository bookmark/BMAD-METHOD-EXP (90 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,012 tokens. A static security scan graded it A with 0 findings. It is 92% identical to analyst, differing in 142 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.