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-post-callgit 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-post-call)<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-post-call"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-post-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/arrowshq/arrows-sales-skills/arrows-post-call"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-post-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.00165 | $0.05066 |
| Opus 5.5 | $0.00066 | $0.02026 |
| Sonnet 5.5 | $0.00033 | $0.01013 |
| Haiku 4.5 | $0.00016 | $0.00507 |
Grade A, and why
arrows-post-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 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What the person does right after hanging up, done for them:
| Output | What's in it |
|---|---|
| Follow-up email | In their voice, built on what the buyer actually said, with next steps, owners and dates |
| CRM update | Next step, stage, competitors mentioned, other fields the call answered, follow-up tasks with dates, and a short call note. Uses the CRM's own field names. Applied only after they approve the exact changes |
| Resources to send | Only when the buyer asked for something a real page on their website answers |
| Gaps | What the next call needs to find out, as questions to ask |
Step 1: Find the call
Don't ask which call when there's one obvious answer. Every extra back-and-forth right after a call is where people give up and write the email themselves.
- Transcript or notes pasted: that's the call. Take the company and attendees from it and keep going. If it doesn't name them and you can't match a deal, use [Company] and [Buyer] placeholders and say so in one line rather than asking; they can swap names in before sending.
- Otherwise: look in the call recorder (or the calendar) for external calls that ended in the last 48 hours (7 days if nothing turns up), filtered by company or date if given.
Then:
- One clear match (the most recent external call, or the only one for that company): go straight on, and open the output with the call you used so they can redirect.
- Two or more equally likely (say, two buyer calls ended in the last hour and no company was named): list them one line each and ask which. This is the only confirmation.
- Nothing found: say where you looked and ask for the transcript, notes or company. Never reconstruct a call you can't see.
Step 2: Read
Reading budget, so this finishes quickly: the full transcript of this call; summaries (not transcripts) of up to 3 earlier calls with this buyer; the CRM deal, its contacts and the last 10 activities or notes; up to 10 email threads with the attendees; chat only if connected and only for this buyer.
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 · +6 lines a53a2bec7151
- 11d ago Changed · +1 lines d83f80320ecf
- 21d ago Changed · -76 lines · +43 tokens per session 955030e4407c
- 1mo ago First seen · 290 lines · 122 tokens per session scan A d6f990024f9b
arrows-post-call is a skill published in the GitHub repository ArrowsHQ/arrows-sales-skills (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 165 tokens to every session and 5,066 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.