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 eddiebelaval/squire --skill customer-discovery-guidegit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/customer-discovery-guide)<a href="https://agentmods.dev/skills/eddiebelaval/squire/customer-discovery-guide"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/customer-discovery-guide/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/eddiebelaval/squire/customer-discovery-guide"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/customer-discovery-guide.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.00013 | $0.00759 |
| Opus 5 | $0.00006 | $0.00380 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
Customer Discovery Guide 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 7d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Discovery Guide
Guide customer discovery interviews and develop customer insight frameworks
When to Use This Skill
Use this skill when you need to:
- Analyze data and extract insights
- Conduct thorough investigation
- Synthesize complex information
Not recommended for:
- Tasks requiring creative content generation
- business operations
Quick Reference
| Action | Command/Trigger |
|---|---|
| Create customer discovery guide | customer discovery |
| Review and optimize | review customer discovery guide |
| Get best practices | customer discovery guide best practices |
Core Workflows
Workflow 1: Initial Customer Discovery Guide Creation
Goal: Create a high-quality customer discovery guide from scratch
Steps:
- Discovery - Understand requirements and objectives
- Planning - Develop strategy and approach
- Execution - Implement the plan
- Review - Evaluate results and iterate
- Optimization - Refine based on feedback
Workflow 2: Advanced Customer Discovery Guide Optimization
Goal: Refine and optimize existing customer discovery guide for better results
Steps:
- Research - Gather relevant information
- Analysis - Evaluate options and approaches
- Decision - Choose the best path forward
- Implementation - Execute with precision
- Measurement - Track success metrics
Best Practices
-
Start with Clear Objectives Define what success looks like before beginning work.
-
Follow Industry Standards Leverage proven frameworks and best practices in research.
-
Iterate Based on Feedback Continuously improve based on results and user input.
-
Document Your Process Keep track of decisions and outcomes for future reference.
-
Focus on Quality Prioritize excellence over speed, especially in early iterations.
Checklist
Before considering your work complete:
- Objectives clearly defined and understood
- Research and discovery phase completed
- Strategy or plan documented
- Implementation matches requirements
- Quality standards met
- Stakeholders informed and aligned
- Results measured against goals
- Documentation updated
- Feedback collected
- Next steps identified
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.
- 7d ago First seen · 128 lines · 13 tokens per session scan A 0ee30be82269
Customer Discovery Guide is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 759 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
Customer Discovery Guide
Guide customer discovery interviews and develop customer insight frameworks.
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…
acquire-skills
Find and install skills for what you're doing — tech or reasoning gaps. Matches activity and tech context to relevant skills. Use when entering unfamiliar tech, stuck on a reasoning challenge, or no skill fits.
discovery-distribution
Run the discovery → synthesis → build → verify → elite-package → distribute loop to turn domain insight into a multi-surface, verified GitHub product. Use when productizing an idea, packaging agentic systems, or raising a repo to elite open-source standards before launch.
retrospective
Store a learning — classify type, route to canonical destination. Use after discoveries, unexpected issues, workarounds, or when a reusable pattern emerges.
web-research-workflow
Unified decision tree for web research and competitive monitoring. Auto-selects WebFetch, Tavily, or agent-browser based on target site characteristics and available API keys. Includes competitor page tracking, snapshot diffing, and change alerting. Use when researching web content, scraping, extracting raw markdown…