Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add naderelewa/Product-to-Prod/plugin install product2prodWrote 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/naderelewa/product-to-prod/init)<a href="https://agentmods.dev/skills/naderelewa/product-to-prod/init"><img src="https://agentmods.dev/badge/skills/naderelewa/product-to-prod/init/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/naderelewa/product-to-prod/init"><img src="https://agentmods.dev/badge/skills/naderelewa/product-to-prod/init.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.00228 | $0.08073 |
| Opus 5 | $0.00114 | $0.04036 |
| Sonnet 5 | $0.00046 | $0.01615 |
| Haiku 4.5 | $0.00023 | $0.00807 |
Grade A, and why
init 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 — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.
init, the consent gate, the receipts, and the removal path
You are the INSTALLER. You ask, you verify, you record. Three hard rules:
- Never assert a gate passed. Run its command and quote the real output. A gate with no receipt is a FAIL, not a pass.
- Never act on a consent gate without an explicit "yes" typed by the user in this conversation. There is exactly one consent gate here, T3, permission to record data about them, and its default is NO. Silence, "sounds good", a thumbs-up, or an inference from earlier context is not consent. One further gate, I1, is an offer rather than a consent: it connects an optional outside integration. It is not permission to record anything, but it takes a typed yes on the same terms and defaults to NO in the same way.
- Fail loudly, never silently. A gate that could not run is printed as FAILED or SKIPPED with its reason. The failure this must never have is a setup that reports success while nothing was written, or, worse, one that reports "off" while a log is being kept.
$ARGUMENTS may be empty (the full run), --verify (ask nothing, re-run every verification,
print the report), or --uninstall (the removal path: print the plan, get the typed phrase, then
remove).
What this skill is NOT. It does not set up the product, and it does not ask you to choose anything the product needs in order to work. Every verb in this plugin runs with nothing configured, nothing consented, and nothing connected. This setup exists for exactly two things that are off until someone turns them on: the component that writes a file about your usage (gates T1–T5), and the one optional outside integration this plugin can be connected to (gate I1). If a user asks for setup and wants neither, the honest answer is "then there is nothing to set up", and you say it in those words.
The numbers, derived, never typed
6 labelled gates in two series: T1 · T2 · T3 · T4 · T5 and I1.
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 · 522 lines · 228 tokens per session scan A fcb549f229a1
init is a skill published in the GitHub repository naderelewa/Product-to-Prod (43 stars, last pushed yesterday), licensed MIT. It adds 228 tokens to every session and 8,073 once invoked, about $0.0011 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.