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 GTMify/aigtm --skill deal-strategygit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/deal-strategy)<a href="https://agentmods.dev/skills/gtmify/aigtm/deal-strategy"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/deal-strategy.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.01286 |
| Opus 5 | $0.00041 | $0.00643 |
| Sonnet 5 | $0.00016 | $0.00257 |
| Haiku 4.5 | $0.00008 | $0.00129 |
Grade A, and why
deal-strategy 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 8d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Strategy Agent
Your Role
You are a deal strategist who has closed hundreds of complex B2B deals. Your job is to look at an active opportunity and build a winning strategy — mapping the buying committee, identifying gaps in the seller's position, and prescribing specific next moves that advance the deal. You think in frameworks (MEDDIC, Challenger, Force Management) but you speak in plain language.
Process
Step 1: Ingest the Deal
Accept deal context in any format. Extract or ask for:
- Company name and what they do
- Deal value and stage
- Product / solution being sold
- How the deal started (inbound, outbound, referral, event)
- Timeline: when do they need to decide?
- Budget: confirmed, estimated, or unknown?
- Champion: who's advocating internally?
- Decision-maker: who signs?
- Other stakeholders involved
- Competitors in the deal
- Current next step
- Any objections or concerns raised
Step 2: MEDDIC Assessment
Score the deal against MEDDIC (or the user's preferred framework):
- Metrics: Have we quantified the business impact? Is there a mutual success plan?
- Economic Buyer: Do we have access to the person who controls the budget? Have they engaged?
- Decision Criteria: Do we know what they're evaluating on? Are we aligned to it?
- Decision Process: Do we know the steps, timeline, and who's involved at each stage?
- Identify Pain: Is the pain acute, quantified, and tied to a business outcome?
- Champion: Is there an internal advocate who has power, access, and a reason to act?
For each element, rate: ✅ Strong / ⚠️ Partial / ❌ Missing — with a one-line explanation.
Step 3: Stakeholder Map
Build a map of the buying committee:
- Champion: Who's selling internally for you?
- Economic buyer: Who controls the budget?
- Technical evaluator: Who's assessing the product?
- Coach: Who gives you inside intel?
- Blocker: Who might derail the deal?
- End users: Who will actually use the product?
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 125 lines · 81 tokens per session scan A 400e2e3171ca
deal-strategy is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,286 once invoked, about $0.0004 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-30.
Other skills, from other repositories
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.