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 fmind/dotfiles --skill product-loopgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/fmind/dotfiles/product-loop)<a href="https://agentmods.dev/skills/fmind/dotfiles/product-loop"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/product-loop/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/fmind/dotfiles/product-loop"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/product-loop.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.00053 | $0.04420 |
| Opus 5.5 | $0.00021 | $0.01768 |
| Sonnet 5.5 | $0.00011 | $0.00884 |
| Haiku 4.5 | $0.00005 | $0.00442 |
Grade A, and why
product-loop 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 1mo 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Loop
One product decision cycle in four phases: Discover what deserves building, Specify what must be true, Launch to a bounded audience, then Learn whether the bet paid. Enter at the phase the evidence supports and stop at the next decision, rather than running all four by default.
Phase Selection
| Situation | Phase |
|---|---|
| The problem, demand, or wedge is still unproven | Discover |
| Discovery is validated and behavior must be pinned down | Specify |
| The change is built and needs a staged audience | Launch |
| The experiment, launch, or sales attempt has produced results | Learn |
Entering the wrong phase is the common failure: writing requirements for an unvalidated problem, or claiming lessons from a launch that never shipped. Name the phase and its evidence before starting.
Ground Rules
These apply to every phase.
- Separate observations, supplied evidence, inferences, and assumptions. Never convert enthusiasm into proof.
- Treat market size, demand, willingness to pay, and competitor claims as current facts that require primary evidence.
- Do not invent quotes, logos, metrics, demand, research, legal requirements, availability, or support capacity.
- Do not contact customers, create accounts, mutate a CRM or analytics, publish pages, buy ads, or spend money without explicit authorization.
- Planning an interview is read-only. Contacting or recording a person, retaining identifiable notes, or publishing a quote requires explicit authorization, applicable consent, and a stated data-retention boundary.
- Scale the artifact to the change. A compact, low-risk decision should not acquire empty sections merely to satisfy a template.
- Scale the dialogue to uncertainty. Proceed when the decision is already clear; ask one high-leverage question when an answer would materially change direction.
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.
- 1mo ago First seen · 183 lines · 53 tokens per session scan A 46ebe70c0dd9
product-loop is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 4,420 once invoked, about $0.0002 per session on Opus 5.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
acli
Search, plan, and update Atlassian Jira and Confluence with acli.
github-issues
Plan, draft, update, link, and close GitHub issues.
bf
Search, read, and update Brain Framework brains (bf): project notes, decisions, actions, and collected mail, calendar, Git, chat, and agent-session records.
product-management
Run product discovery, PRDs, launches, and learning; decide build or stop.
agent-project
Set up repository AGENTS.md, shared skills and agents, host bridges, discovery, and vendor skills.
project-scaffolding
Create repos and licenses; author Copier, Cookiecutter, or Cruft templates and apply their updates.