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 tupe12334/instinct --skill spin-sellinggit clone --depth 1 https://github.com/tupe12334/instinctWrote 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/tupe12334/instinct/spin-selling)<a href="https://agentmods.dev/skills/tupe12334/instinct/spin-selling"><img src="https://agentmods.dev/badge/skills/tupe12334/instinct/spin-selling.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.1 | $0.00027 | $0.02554 |
| Opus 5 | $0.00014 | $0.01277 |
| Sonnet 5 | $0.00005 | $0.00511 |
| Haiku 4.5 | $0.00003 | $0.00255 |
Grade A, and why
spin-selling 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 6d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPIN Selling
Overview
SPIN Selling is a research-backed sales questioning framework developed by Neil Rackham from analysis of 35,000 sales calls. Instead of pitching features, the seller asks four types of questions in sequence to make the buyer feel — and articulate — the full weight of their problem before any solution is mentioned.
┌──────────────────────────────────────────────────────────────┐
│ S ──► P ──► I ──► N │
│ │
│ Situation Problem Implication Need-Payoff │
│ (facts) (pain) (consequences) (buyer sells │
│ themselves) │
│ │
│ LOW value MEDIUM HIGH value HIGHEST value │
│ questions value questions questions │
└──────────────────────────────────────────────────────────────┘
SPIN works because buyers commit to solutions they have articulated themselves. The seller's job is to surface and amplify the problem until the buyer requests help — not to persuade.
Question Types
S — Situation Questions
Gather factual context about the buyer's current state. These are necessary but low-value; use them sparingly because they bore prospects who have answered them before.
Goal: establish baseline facts needed to ask smart Problem questions.
Examples:
- "How many people are currently handling your invoicing process?"
- "What CRM system are you running today?"
- "How long has this team been structured this way?"
Rule: do your research beforehand. Asking questions you could have answered with 10 minutes of prep signals laziness and burns trust.
P — Problem Questions
Uncover difficulties, frustrations, and dissatisfactions with the current situation. This is where implicit need begins to surface.
Goal: get the buyer to acknowledge a specific, named problem.
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.
- 6d ago First seen · 180 lines · 27 tokens per session scan A 130b1d1a6317
spin-selling is a skill published in the GitHub repository tupe12334/instinct (1 stars, last pushed 20d ago), licensed MIT. It adds 27 tokens to every session and 2,554 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-08-31.
Other skills, from other repositories
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
thinking-lindy-effect
Use when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.
thinking-kepner-tregoe
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.