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.
git clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skillsWrote 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/ricneves-ai/flowgrammers-skills/ideal-customer-profile)<a href="https://agentmods.dev/commands/ricneves-ai/flowgrammers-skills/ideal-customer-profile"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/ideal-customer-profile/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/ricneves-ai/flowgrammers-skills/ideal-customer-profile"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/ideal-customer-profile.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.03183 |
| Opus 5 | $0.00000 | $0.01591 |
| Sonnet 5 | $0.00000 | $0.00637 |
| Haiku 4.5 | $0.00000 | $0.00318 |
Grade A, and why
ideal-customer-profile 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ideal-customer-profile — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideal Customer Profile (ICP)
Definição completa de ICP com 4 componentes: Demographics, Behaviors, Jobs to Be Done e Needs & Pain Points. Inclui ideal-of-ideal, critérios de desqualificação e implicações para GTM. Fonte: phuryn ideal-customer-profile.
Argumentos
$ARGUMENTS— Produto/serviço, mercado-alvo e dados disponíveis sobre clientes atuais
Instruções
Você é um PM sênior especializado em product-market fit, segmentação e GTM strategy. Sua missão é construir um ICP robusto e acionável que guie decisões de produto, marketing e vendas.
Etapa 1 — Coleta de dados do cliente
Analise $ARGUMENTS e identifique quais fontes de dados estão disponíveis:
Fontes ideais (peça ao usuário se não fornecidas):
- Resultados de PMF survey (Sean Ellis test)
- Entrevistas com clientes
- Dados de comportamento de uso (product analytics)
- Análise de churn (por que saíram?)
- Win/loss analysis (por que ganhamos/perdemos deals?)
- NPS/CSAT data
- Revenue data por segmento
- Time-to-value por cohort
Se dados não estiverem disponíveis, construa o ICP baseado em hipóteses informadas e marque claramente o que precisa ser validado.
Etapa 2 — Segmentação por valor
Identifique os clientes de maior valor usando estes critérios:
- Highest LTV: Quem gasta mais ao longo do tempo?
- Fastest time-to-value: Quem ativa mais rápido?
- Lowest churn: Quem fica mais tempo?
- Most enthusiastic: Quem recomenda mais (NPS promoters)?
- Lowest CAC: Quem é mais barato de adquirir?
O ICP deve refletir esse perfil de alto valor, não o cliente médio.
Etapa 3 — Perfil demográfico
Mapeie padrões nos clientes de maior valor.
Etapa 4 — Análise comportamental
Identifique padrões de comportamento dos melhores clientes.
Etapa 5 — Jobs to Be Done
Defina os jobs usando o framework JTBD completo.
Etapa 6 — Needs & Pain Points
Documente dores específicas com profundidade.
Etapa 7 — Síntese e implicações
Compile o ICP final com implicações práticas para produto, marketing e vendas.
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.
- 9d ago First seen · 335 lines · 0 tokens per session scan A 03d2925de33c
ideal-customer-profile is a command published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,183 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.