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 lenar-amirov/product-pipeline-public --skill pipeline-stepsgit clone --depth 1 https://github.com/lenar-amirov/product-pipeline-publicWrote 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/lenar-amirov/product-pipeline-public/pipeline-steps)<a href="https://agentmods.dev/skills/lenar-amirov/product-pipeline-public/pipeline-steps"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/pipeline-steps/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/lenar-amirov/product-pipeline-public/pipeline-steps"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/pipeline-steps.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.00067 | $0.00894 |
| Opus 5 | $0.00034 | $0.00447 |
| Sonnet 5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
pipeline-steps 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Step Instructions
Navigation layer: jobs map + registry rules here, per-step details in
references/steps.md (read only the section you are executing).
Jobs → steps. Jobs are the primary interface (CLAUDE.md → JOBS CATALOG):
/hypotheses → steps 1–2 · /brief → 4/5/11 · /validate → 6 ·
/solutions → 7 · /sketch → 8 · /tickets → create-tickets ·
/ingest → skill ingest · /next → skill next-advisor ·
/challenge → skill challenge · /deep-think → skill deep-think.
Every job runs standalone: no initiative → work on chat context, type
evidence INFERRED, offer to persist afterwards; initiative exists → read and
write its registry and artifacts as described per step.
Hypothesis registry (all steps). Hypothesis STATE (status, evidence type,
confidence, sources, history) lives in output/hypotheses.json — manage it via
python3 tools/scripts/hypotheses.py (add / set / validate / render).
set records history automatically. Narrative markdown (hypotheses.md,
validated-hypotheses.md) stays authored prose and must not contradict the
registry. After changing the registry run hypotheses.py render <dir> to
refresh output/registry.md. Legacy initiatives: convert once with
python3 tools/scripts/migrate-hypotheses.py <dir>.
Step index
Details for every step live in references/steps.md — read the section
for the step you are executing (table of contents at the top; don't load
other steps, they aren't needed).
| # | Command | Type | Note |
|---|---|---|---|
| 0 | /setup-initiative |
Core | |
| 1 | /analyze-cjm |
Core | |
| 2 | /synthetic-research |
Recommended | |
| 3 | /competitor-research |
Recommended | |
| 4 | /generate-research |
Recommended | |
| 5 | /create-survey-audience |
Optional | |
| 6 | /validate-problems |
Core | |
| 7 | /solution-hypotheses |
Core | |
| 8 | /sketch-solution |
Core | |
| 8.5 | /user-test-concept |
Optional; alias for user-testing concept mode | |
| 9 | /review-design |
Recommended | |
| 10 | /create-presentation |
Core | Problem Research Report |
| 11 | /create-design-brief |
Recommended | |
| 12 | /estimate-with-dev |
Core | |
| 13 | /finalize-prd |
Core | |
| 14 | /design-ab-test |
Recommended | |
| 15 | /create-gate2-presentation |
Core | Solution Research Report |
| — | /create-tickets |
after Gate 2 | push to tracker via MCP |
| 16 | /analyze-ab-test |
Recommended | |
| 17 | /plan-gtm |
Core | |
| 18 | /create-gtm-materials |
Optional | |
| 19 | /support-task |
Optional |
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 · 66 lines · 67 tokens per session scan A a3b7c34f36f4
pipeline-steps is a skill published in the GitHub repository lenar-amirov/product-pipeline-public (12 stars, last pushed 22d ago), licensed MIT. It adds 67 tokens to every session and 894 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-30.
Other skills, from other repositories
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…