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 gnurio/nurijanian-skills --skill reasons-people-buygit clone --depth 1 https://github.com/gnurio/nurijanian-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/skills/gnurio/nurijanian-skills/reasons-people-buy)<a href="https://agentmods.dev/skills/gnurio/nurijanian-skills/reasons-people-buy"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/reasons-people-buy/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/gnurio/nurijanian-skills/reasons-people-buy"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/reasons-people-buy.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.00073 | $0.00641 |
| Opus 5 | $0.00036 | $0.00320 |
| Sonnet 5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
reasons-people-buy 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 12d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reasons people buy
People buy to move toward a feeling or an outcome, never to own a feature. Copy that names what a product is or does leaves the reader to supply the reason themselves, and most won't. Name the reason first; let the feature prove it.
The move
For every line meant to persuade:
- Name the reason. Match the line to a reason on the list below. A line that maps to none is feature-speak — cut it or rewrite it. Done when every retained line traces to one named reason.
- Say the outcome, not the mechanism. What the buyer gets ("stop losing an hour a day to this"), not how it works ("automated workflow engine").
- Lead with the reason, prove with the feature. Reason in the headline or first line; the feature sits underneath as evidence.
The list
The working spine — 15 reasons people buy stuff:
- To avoid effort
- To feel happier
- To save time
- To be comfortable
- To escape pain or guilt
- To make money
- To save money
- To get recognition
- To be healthier
- To feel secure
- To alleviate fear
- To feel special
- To increase status
- To feel loved
- To get knowledge
Beneath every reason sits one of eight deeper drives (Josh Kaufman, The Personal MBA) — the reason wearing work clothes:
money · status · power · love · knowledge · protection · pleasure · excitement
Write from the 15; check against the 8 that you've found the real driver rather than a surface benefit.
Checks
- One primary reason per asset. A page that argues five reasons equally makes the reader feel none. Pick the primary; demote the rest to support.
- Match the reason to the journey stage. Effort, time, pain, guilt, and fear pull people who don't yet know they have a problem; recognition, status, love, and feeling special close people already deciding.
- Test the phrasing against how a real buyer talks — their vocabulary, not yours. Language accuracy is what makes a line land; guessed language reads as an ad and gets skipped.
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.
- 12d ago First seen · 57 lines · 73 tokens per session scan A 5276bca209f5
reasons-people-buy is a skill published in the GitHub repository gnurio/nurijanian-skills (107 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 641 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…