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 aidi1723/safe-agent-skills --skill business-agile-product-owner-reviewgit clone --depth 1 https://github.com/aidi1723/safe-agent-skillsWrote 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/aidi1723/safe-agent-skills/business-agile-product-owner-review)<a href="https://agentmods.dev/skills/aidi1723/safe-agent-skills/business-agile-product-owner-review"><img src="https://agentmods.dev/badge/skills/aidi1723/safe-agent-skills/business-agile-product-owner-review/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/aidi1723/safe-agent-skills/business-agile-product-owner-review"><img src="https://agentmods.dev/badge/skills/aidi1723/safe-agent-skills/business-agile-product-owner-review.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.00032 | $0.00356 |
| Opus 5 | $0.00016 | $0.00178 |
| Sonnet 5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
business-agile-product-owner-review 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 12d 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.
What it actually says
Agile Product Owner Review
When To Use
Use this draft when reviewing the agile-product-owner metadata-only
candidate from claude-skills before deciding whether to author a local
OneCode skill, merge it into an existing skill, or keep it reference-only.
Safe Workflow
- Identify the task, audience, owner, source domain, target catalog category, and expected artifact.
- Compare the candidate with existing trusted Safe-Agent-Skills to avoid duplicate or overlapping guidance.
- Draft local OneCode guidance from project requirements and operator review; do not copy upstream skill bodies.
- Check provenance, license notes, runtime permissions, and connector assumptions before import.
- Produce an adoption recommendation only; Do not execute upstream content or mark this draft trusted.
Expected Output
- metadata-only candidate summary
- overlap and merge recommendation
- local authoring notes
- required verifier checklist
- adoption decision: convert, merge, keep reference-only, or reject
Verifier Expectations
- metadata-only boundary check
- duplicate skill check
- provenance and license check
- import, serial approval, schema-check, maintain-check, and verify before trust
Draft Metadata
- upstream candidate:
agile-product-owner - source domain:
product-team - source path:
product-team/agile-product-owner/skills/agile-product-owner - mapped category:
business - score:
51 - priority:
P3 - adoption before draft:
reference_only
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 51 lines · 32 tokens per session scan A 65570f27ee90
business-agile-product-owner-review is a skill published in the GitHub repository aidi1723/safe-agent-skills (2 stars, last pushed 20d ago), licensed Apache-2.0. It adds 32 tokens to every session and 356 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…