Borrowing it
Nothing to install: this file belongs to naderelewa/Product-to-Prod. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/naderelewa/Product-to-Prod/main/AGENTS.mdgit clone --depth 1 https://github.com/naderelewa/Product-to-ProdWrote 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/instructions/naderelewa/product-to-prod/agents-md)<a href="https://agentmods.dev/instructions/naderelewa/product-to-prod/agents-md"><img src="https://agentmods.dev/badge/instructions/naderelewa/product-to-prod/agents-md/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/instructions/naderelewa/product-to-prod/agents-md"><img src="https://agentmods.dev/badge/instructions/naderelewa/product-to-prod/agents-md.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.02913 | $0.02913 |
| Opus 5 | $0.01456 | $0.01456 |
| Sonnet 5 | $0.00583 | $0.00583 |
| Haiku 4.5 | $0.00291 | $0.00291 |
Grade A, and why
Product-to-Prod AGENTS.md 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For agents running this plugin
This file is the whole protocol in one place, so that a harness which does not auto-load plugin
skills still runs the engine correctly. If your harness reads skill metadata (name, description,
triggers) on its own, use it, and treat this file as the spine those skills share. If it does not,
this file plus skills/pm-start/SKILL.md is enough to start: read this, read that, route, and open
the routed verb's own file when you get there.
You are helping somebody decide what to build and prove whether it worked. The work is product management: requirements, prioritisation, go-to-market, post-release verification. The engine's value is not that it writes documents quickly. It is that every claim in what it writes is either sourced or labelled as unsourced, and that no gate is passed by the agent that wants to pass it.
What ships here
| Piece | What it is |
|---|---|
skills/pm-start/ |
the dispatcher: interviews in plain words, locks context, routes to exactly one verb |
skills/pm-requirements-v1/ |
a feature from strategy statement to an evidence-tagged handoff package |
skills/pm-portfolio-v1/ |
a batch of asks to a scored, prioritised verdict |
skills/pm-gtm-v1/ |
a go-to-market plan, config-only, no spend and no platform writes |
skills/pm-verify-release-v1/ |
a shipped release graded against its pre-declared acceptance scenarios |
skills/gtm-domain-library/ |
the generic framework library the verbs open one section at a time |
skills/init/ |
first-run setup, including the off-by-default local logging consent |
scripts/ |
the mechanical gates: preflight.sh, hostcheck.sh, tag-lint.sh, inference-gate.sh, publish-lint.sh, release.sh, telemetry.sh |
config/ |
packs.json (context registry) · local.template.json (every host-specific key, all null) · dependencies.json (per-verb capabilities) · denylist.txt (the publish gate's rules) |
packs/ |
the context-pack mechanism, shipping one fictional template pack |
docs/ |
the six documents the README opens into: the wizard and package anatomy, outputs, examples by industry, configuration, the full comparison, the usage log |
| everything else at the root | .claude-plugin/plugin.json (what a harness reads to install this), config.schema.json, README.md, AGENTS.md, LICENSE, .gitignore, references/ (shared reference files) and tests/ (the check suite) |
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 · 169 lines · 2,913 tokens per session scan A fd2bcc73c210
Product-to-Prod AGENTS.md is an instructions file published in the GitHub repository naderelewa/Product-to-Prod (43 stars, last pushed yesterday), licensed MIT. It adds 2,913 tokens to every session, about $0.0146 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).