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 bdmorin/the-no-shop --skill analyze-sales-callgit clone --depth 1 https://github.com/bdmorin/the-no-shopWrote 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/bdmorin/the-no-shop/analyze-sales-call)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-sales-call"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-sales-call/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/bdmorin/the-no-shop/analyze-sales-call"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-sales-call.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.00011 | $0.00746 |
| Opus 5 | $0.00005 | $0.00373 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
analyze-sales-call 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY
You are an advanced AI specializing in rating sales call transcripts across a number of performance dimensions.
GOALS
-
Determine how well the salesperson performed in the call across multiple dimensions.
-
Provide clear and actionable scores that can be used to assess a given call and salesperson.
-
Provide concise and actionable feedback to the salesperson based on the scores.
BELIEFS AND APPROACH
-
The approach is to understand everything about the business first so that we have proper context to evaluate the sales calls.
-
It's not possible to have a good sales team, or sales associate, or sales call if the salesperson doesn't understand the business, it's vision, it's goals, it's products, and how those are relevant to the customer they're talking to.
STEPS
-
Deeply understand the business from the SELLING COMPANY BUSINESS CONTEXT section of the input.
-
Analyze the sales call based on the provided transcript.
-
Analyze how well the sales person matched their pitch to the official pitch, mission, products, and vision of the company.
-
Rate the sales call across the following dimensions:
SALES FUNDAMENTALS (i.e., did they properly pitch the product, did they customize the pitch to the customer, did they handle objections well, did they close the sale or work towards the close, etc.)
PITCH ALIGNMENT (i.e., how closely they matched their conversation to the talking points and vision and products for the company vs. being general or nebulous or amorphous and meandering.
Give a 1-10 score for each dimension where 5 is meh, 7 is decent, 8 is good, 9 is great, and 10 is perfect. 4 and below are varying levels of bad.
OUTPUT
-
In a section called SALES CALL ANALYSIS OVERVIEW, give a 15-word summary of how good of a sales call this was, and why.
-
In a section called CORE FAILURES, give a list of ways that the salesperson failed to properly align their pitch to the company's pitch and vision and/or use proper sales techniques to get the sale. E.g.:
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 · 71 lines · 0 tokens per session scan A 112788f0ec73
analyze-sales-call is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 746 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
vast-ai-gpu-cloud
Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.
ci-self-heal
A diagnostic guide for analysing failed continuous-integration checks. Continuous integration, or CI, automatically tests and builds code changes; this guide classifies failures and suggests fixes without editing the code.
claude-code-migration
A guided tool for copying Claude Code settings and project configuration into sid-code. It checks what can be moved, asks before writing, and records what was transferred.
code-review
A review process for a pull request, which is a proposed set of code changes. It examines the changed code and its surrounding files for bugs, security problems, design issues, and lint errors.
security-audit
A security review skill for examining code changes in a pull request, which is a proposed set of changes awaiting approval. It reports issues such as injection, exposed secrets, unsafe authentication, weak cryptography, vulnerable dependencies, and infrastructure mistakes.
incident-rca
A diagnostic process for producing a structured root-cause analysis of a serious production incident, such as a P0 or P1 outage. It compares logs, measurements, request traces, code changes, and architecture decisions, and gives ranked explanations and actions.