Borrowing it
Nothing to install: this file belongs to freegyes/project-ContemPlace. 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/freegyes/project-ContemPlace/main/.claude/commands/product-intake.mdgit clone --depth 1 https://github.com/freegyes/project-ContemPlaceWrote 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/commands/freegyes/project-contemplace/product-intake)<a href="https://agentmods.dev/commands/freegyes/project-contemplace/product-intake"><img src="https://agentmods.dev/badge/commands/freegyes/project-contemplace/product-intake/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/commands/freegyes/project-contemplace/product-intake"><img src="https://agentmods.dev/badge/commands/freegyes/project-contemplace/product-intake.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.00000 | $0.01979 |
| Opus 5 | $0.00000 | $0.00989 |
| Sonnet 5 | $0.00000 | $0.00396 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
product-intake 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 10d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product intake
Turn raw experience reports from using the product into agent-ready GitHub issues at the right maturity. The user arrives wearing the user hat — "here's what happened when I used the thing" — and shifts to the product hat to make decisions about maturity, framing, and priority.
Arguments
$ARGUMENTS — optional hint about the area of experience (e.g., "image capture", "multilingual", "gardening results"). Can be empty — the user will describe what happened.
When to use this vs other commands
/product-intake— you used the product and want to turn that experience into tracked issues. The input is "I tried X and here's what happened."/analyze— you have general input to process (session write-ups, error logs, transcripts). Broader, shallower./audit-captures— you want to systematically evaluate capture quality across a sample. Structured evaluation against the philosophy./work-on-issue— you want to implement something that already has an issue.
The key difference from /analyze: product intake goes deep on why the system behaved the way it did (code paths, emergent vs. designed behavior, trust contract implications) and produces issues optimized for cold-start pickup by a future agent session.
Workflow
Phase 1: Listen and separate
If the user hasn't provided input yet, ask for it and wait.
The input is typically voice-dictated, stream-of-consciousness, and may contain multiple unrelated observations in one continuous narrative. Before doing anything else:
- Voice correction — scan for misrecognized words per the user's Wispr Flow preference.
- Identify distinct observations — separate them. Each observation that describes a different behavior, edge case, or use case becomes its own track. Don't merge unrelated observations into one issue.
- For each observation, note:
- What the user did (the action)
- What they expected
- What actually happened
- Whether this was a surprise (positive or negative)
- Any broader use case the user described ("I would like to be able to...")
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.
- 10d ago First seen · 137 lines · 0 tokens per session scan A 5784a435f8f2
product-intake is a command published in the GitHub repository freegyes/project-ContemPlace (3 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,979 tokens. 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 commands, from other repositories
sprint-status
A command that shows a project's current development status, including branches, unfinished work, local changes, stashed files, specification changes, and recent CI/CD results.
retro
A command that reviews a recent development sprint, a short period of planned work, using repository history and development metrics.
triage
Triage and categorize findings for the CLI todo system.
resolve_todo_parallel
Resolve all pending CLI todos using parallel processing.
ship-feature
Close out an in-progress feature — verify-done + brain ship (flip + checkpoint + brain check) + update feature MD + close run note.
template
Manage issue templates for streamlined issue creation.