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 varunk130/ai-gtm-skill-library --skill deal-xraygit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/deal-xray)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/deal-xray"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/deal-xray/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/varunk130/ai-gtm-skill-library/deal-xray"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/deal-xray.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.00068 | $0.00729 |
| Opus 5.5 | $0.00027 | $0.00292 |
| Sonnet 5.5 | $0.00014 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
deal-xray 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 26d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal X-Ray (PROVEN Framework)
Qualification checklists get filled in from memory and optimism. Deal X-Ray asks, for each element, what the buyer has done (not said) to prove it, and scores only the evidence. The output is a risk read and one concrete next step per gap, ready for a forecast call.
Core Principle
Score buyer actions, not rep opinions. "They love it" is a belief; "their CFO joined the pricing call" is proof.
The PROVEN Framework
| Letter | Element | Proof looks like |
|---|---|---|
| P | Pain | The buyer quantified the cost of the problem in their own words or numbers |
| R | Resources | Budget line named, or funding source confirmed by someone who controls it |
| O | Owner | An economic buyer has attended a meeting or replied in writing |
| V | Validation | Technical fit confirmed: pilot results, security review started, integration scoped |
| E | Exit criteria | Written mutual plan with dated steps to signature |
| N | No-decision risk | Buyer articulated why doing nothing is worse than acting now |
Evidence levels per element: 0 none · 1 rep belief · 2 buyer said it · 3 buyer did it (artifact exists).
Proof score = Σ levels / 18 × 100.
| Score | Call |
|---|---|
| 75+ | Commit candidate |
| 50-74 | Best case - close the named gaps first |
| <50 | Pipeline only - do not forecast |
Process
- Gather - CRM notes, call transcripts, emails, mutual plan
- Evidence pass - for each PROVEN element, quote the artifact that proves it or mark the gap
- Score - apply evidence levels; flag any element at 0 as the first gap to close
- Next action - for each gap, one action that would move it up a level, with owner and date
- Forecast note - two sentences: the call, and the single fact that would change it
Output
Save to outputs/deal-xray-[account]-[YYYY-MM-DD].md
| Artifact | Description |
|---|---|
| Evidence table | Element, level, quoted proof or "gap" |
| Proof score + call | 0-100 with commit / best case / pipeline |
| Gap plan | Action, owner, date per gap |
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.
- 26d ago First seen · 64 lines · 68 tokens per session scan A 3716da2667f4
deal-xray is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (7 stars, last pushed 12d ago), licensed MIT. It adds 68 tokens to every session and 729 once invoked, about $0.0003 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-09-20.
Other skills, from other repositories
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.