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 emichy/product-judgment --skill make-it-landgit clone --depth 1 https://github.com/emichy/product-judgmentWrote 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/emichy/product-judgment/make-it-land)<a href="https://agentmods.dev/skills/emichy/product-judgment/make-it-land"><img src="https://agentmods.dev/badge/skills/emichy/product-judgment/make-it-land/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/emichy/product-judgment/make-it-land"><img src="https://agentmods.dev/badge/skills/emichy/product-judgment/make-it-land.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.00126 | $0.00633 |
| Opus 5 | $0.00063 | $0.00316 |
| Sonnet 5 | $0.00025 | $0.00127 |
| Haiku 4.5 | $0.00013 | $0.00063 |
Grade A, and why
make-it-land 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 8d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make it land
Turn rambling into a message that moves a decision. Direct, no hedge — same
voice as pressure-test-a-bet.
House style
Answer first, in one sentence. Then only the evidence that carries it. Evidence is selected, not gathered — the two quotes that carry it, not the six that mention it. Every section earns its place by changing what they'd do this week; if it doesn't, cut it. Slack, not email. No preamble, no applause, and none of "the move" / "the play" / "the tell" / "the key insight here" / "Here's my take."
Applies to how you talk to them and to the message you draft.
Output contract
| Rule | |
|---|---|
| Line 1 | Insight or ask — not warmup |
| Deliver | Slack-length + paragraph version |
| Bounce | If observed behavior exists, lead with it. If it doesn't, name what the message rests on — customer signal, inference, or conviction. Don't invent proof. |
Structure
Audience → Behavior → Insight → Ask
- Audience — what do they care about right now?
- Behavior — one observed fact. Not a feature. Not a theme.
- Insight — so what?
- Ask — decide / approve / unblock / align. One per message.
One proof point if available: ticket count, anonymized quote, or metric.
Examples
Before: "We've been doing discovery on reporting and customers have mentioned wanting better visibility and we think this could be a big opportunity next quarter…"
After: "Ops managers export to Excel every Monday for a status report their VP never asked for. Ask: one sprint on visibility-without-export, or does [other bet] win? Need a call by Friday."
Before: "Q3 roadmap: Salesforce integration, reporting improvements, and some performance work. Let me know if you have questions."
After: "Q3 is one bet: deal context stops dying between our tool and the CRM — reps copy-paste notes today, and 3 of 5 recent churns dropped off when deals got complex. Reporting and perf slip to Q4. Say something now if that breaks a commitment you've made."
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.
- 8d ago First seen · 54 lines · 126 tokens per session scan A 74e91aa9b4b2
make-it-land is a skill published in the GitHub repository emichy/product-judgment (4 stars, last pushed 22d ago), licensed MIT. It adds 126 tokens to every session and 633 once invoked, about $0.0006 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-31.
Other skills, from other repositories
first-customer-finder
Find and qualify evidence-backed potential first customers, early adopters, design partners, or beta users for a startup using recent public pain and buying signals. Use when Codex needs to analyze a product URL or idea, define an ideal customer profile, research public discussions and business pages, identify…
gingiris-user-interview
A playbook for interviewing users and operating an early product launch, including screening participants, running interviews, testing beta versions, and reviewing churn. It is based on a described process for finding product-market fit, meaning a product consistently meeting a real user need.
gr-user-interview
A framework for interviewing users to discover product-market fit, meaning a strong match between a product and a real user need.
run-customer-discovery
Use when validating a startup idea, product hypothesis, or new feature by conducting structured interviews with target customers before building.
jtbd-extractor
Turn raw research into Jobs-to-be-Done statements showing what users are really trying to accomplish. Use when: extract jobs, jtbd analysis, jobs to be done, what job is the user hiring, underlying user needs.
stage-map
This skill should be used when a founder wants to know which startup stage they're actually in, what the goal and exit criteria of that stage are, what failure modes to watch for, or which tool/module to use next — e.g. "what stage am I at", "what should I focus on now", "am I ready for an MVP", "do I have…