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 OutlineDriven/outline-driven-development --skill buyer-objection-researchgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/buyer-objection-research)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/buyer-objection-research"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/buyer-objection-research/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/outlinedriven/outline-driven-development/buyer-objection-research"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/buyer-objection-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00900 |
| Opus 5 | $0.00015 | $0.00450 |
| Sonnet 5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
buyer-objection-research 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buyer objection research
Contract
| Field | Bound contract |
|---|---|
| Trigger | Product copy needs buyer-objection evidence collected through approved outreach. |
| Authority | Human-gated: one harness ask/question call before any contact approves the outreach (contacting approved recipients through approved channels, bounded batches, capped interviews); before approval, read-only, producing chat output only. Prose consent, invocation consent, prior-run consent, and post-start discovery do not approve an effect. End the run on scope drift. |
| Side effect | Buyer-objection copy recommendation grounded in anonymized exact language. |
| Done | The evidence supports a copy recommendation, or the concern disappeared, or a non-success terminal applies. |
| Stop | Scope drift; access blocked; interview cap reached; inconclusive evidence. Bound: exact approved recipients in bounded batches, with a total interview cap. |
Inputs
- Approved recipients (required): the exact list of buyers to contact, named before any outreach.
- Interview cap (required): the total number of interviews allowed across all batches.
- Batch size (required): the maximum recipients per batch.
- Approved channels (required): the communication channels permitted for outreach (email, phone, scheduled video call). Named before any contact.
Procedure
- Freeze the recipient list, batch size, interview cap, and approved channels before any contact. Record them in writing. Done when: all four are named and frozen.
- Secure start approval with one harness ask/question call. State the frozen scope: recipients, channels, cap, and batch size. End the run immediately on scope drift. The approval covers the frozen scope only. Done when: approval is collected or the run ends on scope drift.
- Conduct structured interviews within the bound. For each batch:
- Contact recipients only through the approved channels. Do not use a channel outside the frozen list.
- Obtain explicit consent before recording or transcribing. State the purpose: collecting buyer objections to improve product copy. Offer a no-recording option where only notes are taken.
- Follow the interview protocol: open with the product context, ask what nearly stopped them from buying, probe specific objections with follow-up questions, close by asking if the concern dissolved after purchase.
- Collect exact buyer language verbatim. Anonymize identity (remove names, companies, titles). Preserve the objection phrasing.
- Stop at the interview cap without extending it. Done when: interviews are complete, the cap is reached, or access is blocked.
- Analyze collected objections. Group by theme. Identify recurring versus one-off concerns. Distinguish objections that block purchase from concerns that dissolved during the conversation. Done when: objections are themed and classified.
- Synthesize a copy recommendation grounded in the anonymized exact language. Quote the recurring objection phrasing that the copy must address. If the evidence shows the concern disappeared, state that directly. Done when: the recommendation is produced or the evidence is declared inconclusive.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -20 tokens per session d5f310d3782d
- 5d ago First seen · 51 lines · 51 tokens per session scan A e869a4105a71
buyer-objection-research is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 4d ago), licensed Apache-2.0. It adds 31 tokens to every session and 900 once invoked, about $0.0002 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
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
snippet-image-rendering
Use when the user explicitly names snipgrapher and wants code rendered to a polished PNG, SVG, or WebP at an explicit local path. Probes the installed CLI for supported flags and writes only the named image file. Not for other renderers, publishing, or remote actions.