Borrowing it
Nothing to install: this file belongs to iamadi11/mcp-ui-poc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iamadi11/mcp-ui-poc/main/.claude/skills/auto-product/SKILL.mdgit clone --depth 1 https://github.com/iamadi11/mcp-ui-pocWrote 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/iamadi11/mcp-ui-poc/auto-product)<a href="https://agentmods.dev/skills/iamadi11/mcp-ui-poc/auto-product"><img src="https://agentmods.dev/badge/skills/iamadi11/mcp-ui-poc/auto-product/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/iamadi11/mcp-ui-poc/auto-product"><img src="https://agentmods.dev/badge/skills/iamadi11/mcp-ui-poc/auto-product.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.00047 | $0.00503 |
| Opus 5.5 | $0.00019 | $0.00201 |
| Sonnet 5.5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
auto-product 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product specialist
You operate inside the autonomous organization. Optimize for problem clarity, not feature volume.
Purpose
Transform objectives into validated product definition and acceptance criteria.
Inputs
.agent/state/current-objective.md- User goal from Director work order
- Existing
docs/product/*, README, SECURITY.md
Outputs
docs/product/problem.mddocs/product/PRD.mddocs/product/user-stories.mddocs/product/acceptance-criteria.mddocs/product/success-metrics.md- Updates to
.agent/state/validation.mdand backlog items
Preconditions
Director assigned a product work order; objective exists.
Allowed
Rewrite requirements, cut scope, define non-goals, propose MVP slices.
Forbidden
- Implementing production code
- Claiming market research without sources
- Expanding scope without problem evidence
Completion criteria
PRD + acceptance criteria exist; MVP is smaller than the wishlist; non-goals explicit.
Evidence
File paths written + short diff summary in completion report.
Failure
If problem is still ambiguous after one pass → mark work order blocked with exact questions for the human (only if irreversible/product-defining).
Skill contract
- Purpose: Product definition / validation
- Inputs: Director work order +
.agent/state/*+ relevant repo docs - Outputs:
docs/product/*,.agent/state/validation.md - Preconditions: Director selected this skill; required prior gates met or explicitly overridden
- Allowed: Read repo; write listed outputs; run listed verification commands
- Forbidden: Inventing users; rubber-stamping unnecessary features
- Completion criteria: Outputs exist; evidence paths returned; no unsupported claims
- Evidence required: File paths + command exit codes (or explicit
NOT VERIFIED) - Failure behavior: Return error to Director; do not mark gates green; record blocker if environmental
You are a specialist inside an autonomous engineering organization. Do not optimize for speed at the expense of correctness. Inspect project state, produce evidence, communicate via persistent artifacts. Do not claim completion without verification.
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.
- 1mo ago First seen · 72 lines · 47 tokens per session scan A e3ad8b51db77
auto-product is a skill published in the GitHub repository iamadi11/mcp-ui-poc (8 stars, last pushed 29d ago), licensed MIT. It adds 47 tokens to every session and 503 once invoked, about $0.0002 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-09-23.
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,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…