product-status

product-status is a skill for Claude Code from InSciCo/i-framework. It costs 66 tokens per session (615 once invoked), scanned A, original, MIT.

A read-only progress dashboard for a Product folder containing product decisions and feature files. It summarizes stages, gates, feature counts, priorities, and missing links between product goals and features.

In plain words
What is it for?
Use it to review product progress, count and classify features, inspect innovation priorities, and find missing acceptance criteria or unlinked product goals.
Why use it?
It helps spot unfinished work and inconsistencies without changing the product files.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Install

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.

agentmods
npx agentmods add skills/inscico/i-framework/product-status
Any agent
npx skills add InSciCo/i-framework --skill product-status
Clone the repo
git clone --depth 1 https://github.com/InSciCo/i-framework

Made for: Claude Code.

Wrote 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.

agentmods badge for product-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/inscico/i-framework/product-status.svg)](https://agentmods.dev/skills/inscico/i-framework/product-status)
Your own site
<a href="https://agentmods.dev/skills/inscico/i-framework/product-status"><img src="https://agentmods.dev/badge/skills/inscico/i-framework/product-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 615 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.00615
Opus 5 $0.00033 $0.00308
Sonnet 5 $0.00013 $0.00123
Haiku 4.5 $0.00007 $0.00061

Measured 5d ago against content hash 1ea96e160410, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

product-status 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 5d 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.

.claude/skills/product-status/SKILL.md · 32 lines

How it starts

The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/product-status — the dashboard (read-only)

You summarize the whole Product/ folder at a glance. Never modify files — if you find problems, list them as gaps for the founder to fix with the relevant skill.

Procedure

  1. Read everything. The three stage artifacts (and their gate: frontmatter), Product/Features/F*.md (frontmatter + body), Product/features-index.md if present, and Product/competition.md if present.

  2. Compute:

    • Stage/gate completion — which of the three gates are passed vs. open (the risk-burndown line).
    • Feature counts — total, by classification, by priority (MoSCoW), by status.
    • Innovation edge list — innovation features sorted by innovation_weight desc, each with its contributes_to UVP.
    • Weight distribution — are weights spread or clustered?
  3. Run integrity checks (the high-value part) — validate cross-file consistency and list every violation:

    • Dangling UVP reference: a feature's contributes_to value that matches no UVP id in innovation.md.
    • UVP orphan: a UVP element in innovation.md with no innovation feature tracing to it.
    • Classification/weight mismatch: implementation with weight ≠ 0; innovation with weight 0; innovation missing contributes_to.
    • Thin feature: missing a user-story clause, or <3 acceptance criteria.
    • Broken dependency: a depends_on id that points to no existing feature.
    • Portfolio flags: apply the same thresholds as /classify — >40% innovation; and, only when there are ≥3 innovation features, innovation weight span <30 points (skip the spread check below that count).
    • Cherry-picked matrix: if competition.md exists and the "Us" column is ✓ on every row, flag it — a credible comparison has ≥1 row where a rival matches or beats us.
    • Unverified competitor claims: if competition.md exists, count cells marked ? and surface them as items to verify (with the snapshot date).
  4. Render a concise dashboard — a risk-burndown header, a counts table, the ranked edge list, and a clearly separated Gaps / next actions section that names which skill fixes each gap (/feature, /classify, /innovate).

Read the full file on GitHub · 32 lines

Changes

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.

  1. 5d ago First seen · 32 lines · 66 tokens per session scan A 1ea96e160410

Subscribe to this mod's changes

product-status is a skill published in the GitHub repository InSciCo/i-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 615 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.

Related

Other skills, from other repositories

product-brainstorming

Brainstorm product ideas, explore problem spaces, and challenge assumptions as a thinking partner. Use when exploring an opportunity, generating solutions, or stress-testing an idea before converging on a direction.

martineserios/thebrana · 44 tokens

pr

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

umputun/cc-thingz · 51 tokens

backlog

Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…

umputun/cc-thingz · 96 tokens

ask-codex

Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…

umputun/cc-thingz · 103 tokens

clarify

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…

umputun/cc-thingz · 91 tokens

writing-style

Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

umputun/cc-thingz · 52 tokens