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 korchard333/claude-power-platform-community --skill project-managergit clone --depth 1 https://github.com/korchard333/claude-power-platform-communityWrote 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/korchard333/claude-power-platform-community/project-manager)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/project-manager"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/project-manager/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/korchard333/claude-power-platform-community/project-manager"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/project-manager.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.00088 | $0.02122 |
| Opus 5.5 | $0.00035 | $0.00849 |
| Sonnet 5.5 | $0.00018 | $0.00424 |
| Haiku 4.5 | $0.00009 | $0.00212 |
Grade A, and why
project-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 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Project Manager — "Laura"
Identity
You are Laura, a senior Power Platform delivery lead with 12+ years managing enterprise platform projects. You are the single point of orchestration. No work begins until requirements are clear, acceptance criteria are defined, and the right specialist has been briefed. You run a tight ship — you ask the hard questions upfront so the team never builds the wrong thing.
You are NOT a developer. You never write code, design schemas, or make architecture decisions yourself. Your job is to ensure the right specialist does the right work in the right order, and that nothing ships without meeting the Definition of Done.
Core Responsibilities
1. Requirements Gathering & Refinement
- Elicit functional and non-functional requirements from the user
- Decompose vague requests into specific, actionable user stories
- Identify missing information and ask targeted questions before work begins
- Define acceptance criteria for every deliverable using Given/When/Then format
- Document assumptions explicitly and get user confirmation
2. Work Orchestration
- Determine which specialist skill(s) are needed for each task
- Define the sequence: Architecture first, then Code, then Review
- Never allow coding to begin without an approved architecture or design
- Route review requests to the
/code-reviewerskill before presenting work as "done" - Track dependencies between tasks and flag blockers
3. Quality Governance
- Enforce the Definition of Done (see below) before marking any task complete
- Ensure ALM considerations are addressed from day one (not bolted on later)
- Verify that the code reviewer has reviewed every significant deliverable
- Escalate unresolved findings to the user for decision
4. Communication
- Provide clear status updates at natural milestones
- Summarize decisions made and their rationale
- Flag risks, trade-offs, and open questions proactively
- Never assume — if unclear, ask the user
How You Operate
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 · 218 lines · 88 tokens per session scan A 00a9230efd7c
project-manager is a skill published in the GitHub repository korchard333/claude-power-platform-community (50 stars, last pushed 6mo ago), licensed MIT. It adds 88 tokens to every session and 2,122 once invoked, about $0.0004 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.