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 agentmods add skills/ramybarsoum/prodkit/impact-sizingnpx skills add ramybarsoum/prodkit --skill impact-sizinggit clone --depth 1 https://github.com/ramybarsoum/prodkitWrote 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/ramybarsoum/prodkit/impact-sizing)<a href="https://agentmods.dev/skills/ramybarsoum/prodkit/impact-sizing"><img src="https://agentmods.dev/badge/skills/ramybarsoum/prodkit/impact-sizing.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00445 |
| Opus 5 | $0.00011 | $0.00222 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
impact-sizing 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 3d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interaction style: Use the
AskUserQuestiontool for all structured questions in this skill. Group related questions together (2-3 per call) rather than asking one at a time.
/impact-sizing - Quantify Feature Value
Systematically estimate the impact of a feature using the 4-step framework.
Context Routing Logic (Internal - for Claude)
Automatic Context Checks: When this skill is invoked, immediately check:
| Source | Files/Folders | Search Terms | What to Extract |
|---|---|---|---|
| Current PRD | projects/*/ |
feature name from chat | User impact, problem severity |
| User Research | knowledge/research/*.md |
feature problem, user quotes | Addressable users, pain severity |
| Business Model | knowledge/company/business-info.md |
pricing, revenue model, TAM | Revenue impact drivers |
| Historical Data | knowledge/metrics/*.md |
similar features, baseline conversion | Reference adoption rates |
| Strategy | knowledge/strategy/*.md |
feature strategic fit | Resource availability, priority context |
| Product Principles | knowledge/company/product-principles.md |
product principles, core values | Which principles this feature embodies and how |
Context Priority:
- Product principles alignment FIRST
- Feature definition and user impact SECOND
- Business model and pricing THIRD
- User base size and addressable segment FOURTH
- Historical precedent for similar features FIFTH
Cross-Skill Links:
- If sizing is unclear → Link to
/impact-sizing(this skill) - If comparing options → Use this to inform
/experiment-decision - If building business case → Reference in PRD and
/write-prod-strategy - If identifying leading metrics → Connect to
/feature-metricsand/metrics-framework
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.
- 3d ago First seen · 44 lines · 22 tokens per session scan A b4e730471377
impact-sizing is a skill published in the GitHub repository ramybarsoum/prodkit (4 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 445 once invoked, about $0.0001 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.