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-setupgit 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-setup)<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-setup"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-setup/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-setup"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-setup.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.00171 | $0.08761 |
| Opus 5.5 | $0.00068 | $0.03504 |
| Sonnet 5.5 | $0.00034 | $0.01752 |
| Haiku 4.5 | $0.00017 | $0.00876 |
Grade A, and why
arrows-setup 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 7d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builds the profile that makes every Sales Skill write like this person and run deals the way their team does. Four files (five for sales leaders), built from their real data:
| File | What's in it | Personal or team |
|---|---|---|
arrows-voice.md |
How they write and talk: tone, structure, greeting and sign-off, phrases that are theirs, what gets replies, and real examples for each situation (first follow-up, post-demo recap, nudge, pricing, scheduling) | Personal |
arrows-sales-process.md |
Why they win and lose, every stage and what has to be true to move on, methodology, the basic numbers | Team |
arrows-buyers-and-competitors.md |
What they sell and who buys, pricing, each competitor in a line or two | Team |
arrows-how-i-work.md |
What they do on their best deals, where their time goes, what slips, their rules, their tools | Personal |
arrows-how-we-work.md (leaders only) |
The team, handoffs, what every rep does on every deal, what the leader wants to see weekly | Team |
Each skill reads the files it needs: email drafts lean on voice; pipeline reviews lean on process. Reps on a team add the leader's team files, so everyone follows one process while writing in their own voice. Some skills add their own arrows-*.md files later for deeper work; setup doesn't build those.
The person replies twice: once to name their best deals, once to confirm what you found. Everything else comes from the data.
Progress
Start each setup message with a progress line:
Sales Skills by Arrows · Setup ■■■□□ Reading your calls
Squares by stage: Starting □□□□□ · Reading your CRM / Reading your calls / Reading your email ■□□□□ · Studying your best deals ■■□□□ · Here's what I learned ■■■□□ · Building your profile ■■■■□ · Saved ■■■■■. Show the bar once at the top of each message, not on every scan line. As each source finishes, post one line with a real number:
✓ CRM: 46 open deals, 112 closed in the last 6 months
✓ Calls: read your last 10 calls
✓ Email: 28 emails you sent to buyers, and their replies
– Calendar: not connected (skipping meeting context)
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.
- 7d ago Changed · +8 lines fa836f99a9b9
- 11d ago Changed · +1 lines 75c989a516b2
- 21d ago Changed · -63 lines · +104 tokens per session ec27d6a402c7
- 1mo ago First seen · 471 lines · 67 tokens per session scan A 70298ed6017b
arrows-setup is a skill published in the GitHub repository ArrowsHQ/arrows-sales-skills (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 171 tokens to every session and 8,761 once invoked, about $0.0007 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-08-31.
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.