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 jeremylongworth-source/AgentSkills --skill sales-conversion-enablementgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/sales-conversion-enablement)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/sales-conversion-enablement"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/sales-conversion-enablement/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/jeremylongworth-source/agentskills/sales-conversion-enablement"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/sales-conversion-enablement.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.00068 | $0.00435 |
| Opus 5.5 | $0.00027 | $0.00174 |
| Sonnet 5.5 | $0.00014 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
sales-conversion-enablement 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 1mo 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
Sales Conversion Enablement
Core Workflow
- Identify buyer role, stage, pain, desired outcome, buying process, decision criteria, alternatives, and next milestone.
- Prepare discovery around business impact, current process, urgency, constraints, stakeholders, success criteria, and risk.
- Tailor demos and collateral to the buyer's stated problem; avoid feature tours.
- Convert objections into diagnosis: value, risk, timing, trust, fit, authority, procurement, or change management.
- Use mutual action plans for complex deals: steps, owners, dates, dependencies, legal/security/procurement, and success criteria.
- Handoff cleanly to onboarding/customer success with promises, risks, stakeholders, and value case preserved.
Enablement Assets
- Discovery call plan
- Demo flow
- Objection map
- Proposal outline
- Business case
- Mutual action plan
- Competitive positioning
- Post-sale handoff brief
Review Standard
Sales material should help the buyer make a decision, not merely describe the product. Lead with buyer outcomes, proof, risk reduction, implementation path, and cost of inaction.
Freshness Rule
Verify current CRM, e-signature, proposal, procurement, security-review, and enablement-platform documentation before giving platform-specific setup guidance. Keep buyer strategy separate from vendor UI details.
Deliverable Shape
For sales conversion work, provide:
- Deal or buyer context
- Stage and desired next milestone
- Discovery or demo plan
- Buyer-specific value case
- Objection and risk map
- Mutual action plan or proposal outline
- Follow-up and handoff notes
References
- Read
references/conversion-enablement-checklist.mdwhen preparing or reviewing sales conversion work.
What ships with it
2 files 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.
- 1mo ago First seen · 52 lines · 68 tokens per session scan A 27afffe55732
sales-conversion-enablement is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 68 tokens to every session and 435 once invoked, about $0.0003 per session on Opus 5.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
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
analiz-task-spec
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over.
answer-workspace-questions
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval.
call-prep
Create or review call prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for call prep planning or analysis.
wicked-garden-product
Product domain skill: 13 user-invokable actions — a11y | acceptance | align | analyze | elicit | listen | mockup | screenshot | strategy | synthesize | ux | ux-review | visual-direction — backed by the rubrics in refs/ and this domain's knowledge-module sub-skills. Use when: "accessibility audit", "WCAG compliance"…
wicked-garden-swarm
Parallel verification-swarm orchestration playbook: fan out N scoped subagents over N units of work (repos / modules / files), then run a SEPARATE verifier wave that re-derives each result from a clean state — self-graded "done" is rejected. Composes the crew agents, the qe semantic-reviewer, /wicked-garden:prove…