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 ArrowsHQ/arrows-sales-skills --skill arrows-win-loss-analysisgit clone --depth 1 https://github.com/ArrowsHQ/arrows-sales-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/arrowshq/arrows-sales-skills/arrows-win-loss-analysis)<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-win-loss-analysis"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-win-loss-analysis/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/arrowshq/arrows-sales-skills/arrows-win-loss-analysis"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-win-loss-analysis.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.00260 | $0.15069 |
| Opus 5.5 | $0.00104 | $0.06028 |
| Sonnet 5.5 | $0.00052 | $0.03014 |
| Haiku 4.5 | $0.00026 | $0.01507 |
Grade A, and why
arrows-win-loss-analysis 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 — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answers one question from the team's own closed deals: why do we win, and why do we lose? Every number comes from their CRM, calls and email, with the counts on both sides, so it's clear what actually separates a win from a loss.
| Section | What it answers |
|---|---|
| Three things to change this quarter | The changes most likely to raise the win rate, each with the evidence and steps |
| Who wins | Win rate by segment: company size, lead source, industry, the buyer's current tools, existing customers vs. new |
| The moves that win | The 3–5 things that happen on wins and not on losses, counted on both sides, plus what every deal gets that doesn't decide anything |
| Where and why deals die | The stage and timing where losses happen, and the real loss reasons from reading the deals compared with what the CRM says |
| The buying group | Which roles were involved on wins and who was missing on losses |
| Methodology | Which parts of the team's methodology (MEDDPICC, SPICED, BANT or their own) actually predict a win |
| By rep (leaders) | Each rep's win rate and cycle, and what the top rep does that the others don't |
This looks back at closed deals. It isn't a list of open deals to chase this week; that's the process gaps report. A few stalled open deals are read only as a comparison, to show whether today's pipeline looks like the wins or the losses.
It's a deep read: expect 15–30 minutes, with progress shown as it goes. No questions before the report unless the scope is truly unclear.
Progress
Post a progress line at the start and after each pass, with one line per finding and real numbers:
Sales Skills by Arrows · Win-loss analysis ■■□□□ Reading deals end to end
✓ Pipeline: 184 deals closed in the last 12 months (22% win rate), 61 open
✓ Cleaned: left out 14 tests, no-shows and stray bookings
Stages: Counting your closed deals ■□□□□ · Reading deals end to end ■■□□□ · Reading your calls and email ■■■□□ · Comparing wins and losses ■■■■□ · Done ■■■■■.
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 · 535 lines · 260 tokens per session scan A 7604fbfd91b9
arrows-win-loss-analysis is a skill published in the GitHub repository ArrowsHQ/arrows-sales-skills (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 260 tokens to every session and 15,069 once invoked, about $0.0010 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-10-21.
Other skills, from other repositories
ib_0dte
Find and place the best 0DTE (zero-days-to-expiration) credit spreads from Interactive Brokers. Default execution route is the EMA9/EMA21 + VIX/VXN regime strategy (emavix0dte.py), which auto-selects bullput or bearcall from a bare EMA cross and skips the trade when the vol index is elevated (VXN ≥ 30 for NDX/QQQ, VIX…
ib-pmcc-advisor
Analyze PMCC (Poor Man's Covered Call / diagonal spread) positions from IB portfolio. For each diagonal spread, reports short leg risk (delta, IV, assignment probability), daily P&L projections, top-3 roll candidates, and a side-by-side comparison table. Requires TWS or IB Gateway running locally.
ib-stop-loss
Downside stop-loss management for PMCC, naked LEAPS, and stock positions in IB. Computes stop prices, detects alerts, and places conditional combo orders. Dry-run by default. Requires TWS or IB Gateway running locally.
ib-trades-history
Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.
ib-trailing-stop
Server-side trailing stop management for stocks and naked LEAPS in IB. Places native TRAIL orders that auto-ratchet the stop as price climbs. Dry-run by default. Requires TWS or IB Gateway running locally.
scanner-pmcc
Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.