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 cpliakas/claude-code-engineering-leaders --skill onboard-product-ownergit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/onboard-product-owner)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/onboard-product-owner"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/onboard-product-owner/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/cpliakas/claude-code-engineering-leaders/onboard-product-owner"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/onboard-product-owner.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.00064 | $0.01737 |
| Opus 5 | $0.00032 | $0.00869 |
| Sonnet 5 | $0.00013 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
onboard-product-owner 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 11d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard — Product Owner
Configure the Product Owner agent for your project by capturing issue tracker details, backlog norms, and current roadmap state.
Prerequisites
This skill layers on top of shared project context. Before starting, read:
.claude/agent-memory/engineering-leaders/PROJECT.md
Track whether this file exists as shared_context_exists. If it does not
exist, note:
"Shared project context hasn't been set up yet. I can continue with Product Owner-specific questions, but running /onboard first will give all agents a better foundation. Would you like to continue anyway?"
- If the user says yes: track
shared_context_exists = falseand continue to the Output Location section. - If the user says no: stop here. Do not proceed to the interview or write any files. Tell the user: "No problem. Run /onboard first to set up shared project context, then come back to /onboard-product-owner."
Output Location
Product Owner project memory is written to:
.claude/agent-memory/engineering-leaders-product-owner/MEMORY.md
If this file already exists, show the user a brief summary of what is recorded (issue tracker platform, current phase, sizing convention) and ask:
"Product Owner memory already exists. Would you like to:
(a) Update specific sections — I'll ask which sections to replace and re-run only those questions. All other sections are preserved unchanged. (b) Start fresh — I'll run the full interview and replace the entire file when complete. If you abandon the interview before finishing, the original file is left unchanged."
If the user chooses (a):
Show the list of sections (Issue Tracker, Roadmap and Phases, Team Norms) and ask which to update. Re-ask only the questions for those sections (Q1-Q3 for Issue Tracker, Q4-Q6 for Roadmap and Phases, Q7-Q9 for Team Norms), then merge the new answers into the existing file by replacing only those sections. Sections not selected are preserved verbatim from the original. Any content in the file that does not correspond to a template section (e.g., manually added sections) must also be preserved verbatim — do not discard unrecognized content.
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.
- 11d ago First seen · 220 lines · 64 tokens per session scan A adfee2b134ab
onboard-product-owner is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,737 once invoked, about $0.0003 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-31.
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.