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 system-design-docgit 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/system-design-doc)<a href="https://agentmods.dev/skills/lenar-amirov/product-pipeline-public/system-design-doc"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/system-design-doc/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/system-design-doc"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/system-design-doc.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.00092 | $0.00516 |
| Opus 5 | $0.00046 | $0.00258 |
| Sonnet 5 | $0.00018 | $0.00103 |
| Haiku 4.5 | $0.00009 | $0.00052 |
Grade A, and why
system-design-doc 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.
What it actually says
System Design (PM view)
Boundary: this skill = what the system looks like and what constrains the
initiative (feasibility input, PRD §9–10). What will be built for this
initiative belongs to technical-spec-document.
This is a conversation WITH the dev lead, not a document Claude invents. Claude structures; the dev lead supplies facts. Anything Claude infers without the dev lead is INFERRED — mark it and list it as an open question.
What to capture (in priority order)
- System context — which existing components/services does the solution touch? One list: component → what changes.
- Dependencies — teams, internal platforms, external vendors the
initiative needs. For each: owner + what exactly + lead time. These
become
dependencies[]in status.json (owner, deadline, blocks) — offer to create them immediately. - Constraining NFRs — load, latency, privacy/compliance, platform parity. Only the ones that could change the solution shape or the estimate; skip textbook lists.
- Risks and unknowns — the "we won't know until we open it" list; each unknown widens the estimate — ask the dev lead to size the widening.
- Integration points for tracking — where the analytics events (from
tracking-and-funnels) will be emitted; flag anything the solution makes unmeasurable.
Output
output/dev-estimate.md §Architecture (or PRD §9–10 directly): context
list, dependency table, constraining NFRs, risk register with estimate
impact.
Anti-patterns
- Infrastructure detail (servers, databases, configs) the PM neither needs nor can verify.
- Presenting Claude-guessed architecture as fact — without the dev lead everything here is INFERRED.
- NFR laundry lists — only constraints that change decisions.
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 · 47 lines · 92 tokens per session scan A 88a57200c11a
system-design-doc is a skill published in the GitHub repository lenar-amirov/product-pipeline-public (12 stars, last pushed 22d ago), licensed MIT. It adds 92 tokens to every session and 516 once invoked, about $0.0005 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…