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-weekly-pipeline-reviewgit 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-weekly-pipeline-review)<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-weekly-pipeline-review"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-weekly-pipeline-review/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-weekly-pipeline-review"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-weekly-pipeline-review.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.00150 | $0.12914 |
| Opus 5.5 | $0.00060 | $0.05166 |
| Sonnet 5.5 | $0.00030 | $0.02583 |
| Haiku 4.5 | $0.00015 | $0.01291 |
Grade A, and why
arrows-weekly-pipeline-review 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review period: this week
The whole open pipeline on one page, built to be read in 30 seconds and shared before a 1:1 or team pipeline meeting.
| Section | What's in it |
|---|---|
| Header | "[Name]'s weekly pipeline review" (team view: "[Company] weekly pipeline review"), a bar of on track vs. at risk, and four numbers: open deals, on track, at risk, expected to close |
| Moving forward | Deals that advanced, kicked off or won, so the good news is visible too |
| At risk | Deals that are quiet, have no next step, or have a broken promise, each with the reason and one action (the biggest few in a team view) |
| Do this week | The 3–5 moves that matter most, ranked, each opening into numbered steps |
| By rep (leaders) | Each rep's pipeline, at-risk count and the one thing to raise in their 1:1; open a rep for their deals |
| Pipeline by stage | Count and value per stage, plus deals missing what the stage requires |
| Expected to close | Every deal with a close date in the period, with its real state, plus deals that slipped past their date |
| Closed won, closed lost | Each deal won and lost this period, wins as visible as losses |
The default output is a visual report built from one fixed template (end of this skill), so it looks the same every week. A short summary goes in the chat alongside it.
Step 1: Read the profile
Use the profile files if they're in the project. They tell you what "good" looks like for this person, so the review flags what matters to them rather than generic hygiene.
arrows-sales-process.md:## Pipeline stagesgives the stage order, what has to be true to move on, and typical time in stage.## Discovery and qualificationgives the methodology (MEDDIC, SPICED, BANT or their own) and what's usually missing. Use these to judge whether a deal is really where its stage says.arrows-how-i-work.md:## What slipstells you what to flag first.## About mesays rep, leader or both.arrows-how-we-work.md(leaders):## What I want to see weeklyshapes the rollup;## Every rep, every dealis the checklist each rep's deals are measured against.
No profile: run the review anyway with stages straight from the CRM, and use the shared context's one-line setup suggestion at the end.
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 dba319f06bf5
- 11d ago Changed · +1 lines 7c766eae8fab
- 21d ago Changed · +141 lines · +46 tokens per session e84b1420bb1d
- 1mo ago First seen · 342 lines · 104 tokens per session scan A a2e808c2ba5f
arrows-weekly-pipeline-review is a skill published in the GitHub repository ArrowsHQ/arrows-sales-skills (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 150 tokens to every session and 12,914 once invoked, about $0.0006 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.