product-capability

product-capability is a skill for Claude Code, Codex from affaan-m/ECC. It costs 59 tokens per session (906 once invoked), scanned A, original, MIT.

A way to turn product requests or discussions into a clear engineering plan that states required behavior, limits, interfaces, and unanswered questions.

In plain words
What is it for?
Use it when converting a product requirements document, roadmap item, or founder note into implementation-ready guidance.
Why use it?
It exposes hidden assumptions before work crosses multiple services, codebases, or teams.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Codex.

Part of the ecc plugin — 78 skills, 58 commands, 70 agents, 1 MCP server shipped together

Good fit Use it when converting a product requirements document, roadmap item, or founder note into implementation-ready guidance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/affaan-m/ecc/product-capability
About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 287,323 stars · on GitHub · ecc.tools

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.

Any agent
npx skills add affaan-m/ECC --skill product-capability
Clone the repo
git clone --depth 1 https://github.com/affaan-m/ECC

Made for: Claude Code, Codex.

Or install ecc, the plugin that ships this one along with the rest of its 78 skills, 58 commands, 70 agents, 1 MCP server.

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-capability

README.md
[![agentmods](https://agentmods.dev/badge/skills/affaan-m/ecc/product-capability/github.svg)](https://agentmods.dev/skills/affaan-m/ecc/product-capability)
Your own site
<a href="https://agentmods.dev/skills/affaan-m/ecc/product-capability"><img src="https://agentmods.dev/badge/skills/affaan-m/ecc/product-capability/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.

agentmods 80×15 button for product-capability

Your own site · 80×15
<a href="https://agentmods.dev/skills/affaan-m/ecc/product-capability"><img src="https://agentmods.dev/badge/skills/affaan-m/ecc/product-capability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 906 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review Third-party audits
  • Socket pass 16 Jun 2026
  • Snyk warn 16 Jun 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00059 $0.00906
Opus 5.5 $0.00024 $0.00362
Sonnet 5.5 $0.00012 $0.00181
Haiku 4.5 $0.00006 $0.00091

Measured 1mo ago against content hash 1e2386179de6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

product-capability 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.agents/skills/product-capability/SKILL.md · 142 lines

How it starts

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

Product Capability

This skill turns product intent into explicit engineering constraints.

Use it when the gap is not "what should we build?" but "what exactly must be true before implementation starts?"

When to Use

  • A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit
  • A feature crosses multiple services, repos, or teams and needs a capability contract before coding
  • Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy
  • Senior engineers keep restating the same hidden assumptions during review
  • You need a reusable artifact that can survive across harnesses and sessions

Canonical Artifact

If the repo has a durable product-context file such as PRODUCT.md, docs/product/, or a program-spec directory, update it there.

If no capability manifest exists yet, create one using the template at:

  • docs/examples/product-capability-template.md

The goal is not to create another planning stack. The goal is to make hidden capability constraints durable and reusable.

Non-Negotiable Rules

  • Do not invent product truth. Mark unresolved questions explicitly.
  • Separate user-visible promises from implementation details.
  • Call out what is fixed policy, what is architecture preference, and what is still open.
  • If the request conflicts with existing repo constraints, say so clearly instead of smoothing it over.
  • Prefer one reusable capability artifact over scattered ad hoc notes.

Inputs

Read only what is needed:

  1. Product intent
    • issue, discussion, PRD, roadmap note, founder message
  2. Current architecture
    • relevant repo docs, contracts, schemas, routes, existing workflows
  3. Existing capability context
    • PRODUCT.md, design docs, RFCs, migration notes, operating-model docs
  4. Delivery constraints
    • auth, billing, compliance, rollout, backwards compatibility, performance, review policy

Core Workflow

1. Restate the capability

Read the full file on GitHub · 142 lines

Files

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.

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. 1mo ago Changed · +1 lines 1e2386179de6
  2. 1mo ago First seen · 141 lines · 59 tokens per session scan A ae6e95205fcd

Subscribe to this mod's changes

product-capability is a skill published in the GitHub repository affaan-m/ECC (287,323 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 906 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-08-30.