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 agentmods add instructions/tonypls/agentic-product-launch/agents-mdgit clone --depth 1 https://github.com/tonypls/agentic-product-launchWrote 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/tonypls/agentic-product-launch/agents-md)<a href="https://agentmods.dev/instructions/tonypls/agentic-product-launch/agents-md"><img src="https://agentmods.dev/badge/instructions/tonypls/agentic-product-launch/agents-md.svg" alt="Measured on agentmods" 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 | $0.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
agentic-product-launch 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 5d 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.
What it actually says
Agent Instructions
- Prefer
pnpmovernpmfor JavaScript package workflows. - Avoid em dash punctuation in repository content. Use hyphens, colons, commas, or sentence breaks instead.
- For project launch strategy, launch copy, Product Hunt, Show HN, Reddit/community launch planning, direct outreach, launch-day operations, or post-launch follow-up, read
skills/launch-project/SKILL.md. - Launch work is co-creation: interview the builder and co-write in their voice, never hand back fill-in-the-blank templated copy. Recommend the platforms and optimal posting times that fit the specific project.
- Before drafting or revising any public-facing copy, apply
skills/launch-project/references/tone-guide.md- match the builder's tone profile (built from copy they've written before), cut tired words like "opinionated," never narrate a rule being followed ("disclosing upfront"), and keep playbook vocabulary ("permission," "readiness gate") out of public copy. - Keep launch guidance portable across Claude Code, Codex, and other markdown-reading agents.
- Treat
skills/launch-project/references/launch-workflow.mdas the source of truth. Platform-specific wrappers should reference it, not duplicate it. - Before making current platform-rule claims, verify official/current guidance when the launch will actually be run.
- Do not recommend vote requests, fake engagement, undisclosed promotion, engagement pods, sockpuppets, scrape-and-spam outreach, or community-rule workarounds.
- A searchable knowledge store of past solutions lives in
docs/solutions/, organized by category with YAML frontmatter (module,tags,problem_type) - relevant when implementing or debugging in documented areas.
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.
- 5d ago First seen · 13 lines · 358 tokens per session scan A dd79543c1427
agentic-product-launch AGENTS.md is an instructions file published in the GitHub repository tonypls/agentic-product-launch (10 stars, last pushed 1mo ago), licensed MIT. It adds 358 tokens to every session, about $0.0018 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 instructions, from other repositories
dev3000 AGENTS.md
Instructions for vercel-labs/dev3000, covering agents.md, runtime, local ui, production workflows, browser tools and development rules.
agent-inspect AGENTS.md
AGENTS.md instructions for rajudandigam/agent-inspect, covering agentinspect ai maintainer instructions, product boundary, source of truth, public-copy rule and start every task.
jenkins-cli CLAUDE.md
Claude Code instructions for avivsinai/jenkins-cli, covering claude.md, build & test commands, run a single test, skip e2e tests during unit testing and e2e with colima on macos (if docker is unreachable).
patchloom AGENTS.md
AGENTS.md instructions for patchloom/patchloom, covering agents.md, project overview, dev commands, git hygiene and release prs (release-please).
goal-flight AGENTS.md
AGENTS.md instructions for simonrowland/goal-flight, covering agent notes, goal flight routing, project commands (this repo), git workflow (this repo) and git-visible trigger hygiene.
ducklab AGENTS.md
Instructions for jrullan/ducklab, covering working in this repository as an agent and path 1: conventional (edit the tree directly).