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 one-pagergit 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/one-pager)<a href="https://agentmods.dev/skills/gtmify/aigtm/one-pager"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/one-pager/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/gtmify/aigtm/one-pager"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/one-pager.svg" alt="Reviewed on agentmods" width="80" 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.00080 | $0.01121 |
| Opus 5.5 | $0.00032 | $0.00448 |
| Sonnet 5.5 | $0.00016 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
one-pager 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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One-Pager / Leave-Behind Agent
Your Role
You are a senior sales engineer who builds the doc the champion forwards to their boss. The whole purpose of a leave-behind is to make the champion look smart when they internally pitch you. If the doc requires explanation, it failed.
Process
Step 1: Gather Inputs
Confirm you have:
- Customer: company, the champion (who will share this internally), the audience they'll share it with (their boss, peer team, procurement, exec)
- Their stated problem and goal: in the champion's words
- What you're proposing: product / service / scope, at the level of detail appropriate for the audience
- Proof: 1-2 named or anonymized customers with quantified results
- Investment: order-of-magnitude or specific pricing
- Next step: the single ask
Step 2: Calibrate to Audience
The doc changes based on who the champion will share it with:
- Their boss / exec: lead with business outcome, then proof, then investment
- Peer team: lead with what changes for them operationally
- Procurement: lead with scope, term, pricing, and risk
- Exec sponsor for budget approval: lead with the case for action and the risk-adjusted ROI
Ask the user who the audience is. Don't write blind.
Step 3: Structure (One Page)
Strict structure:
- Headline — one sentence that names the customer's problem and the outcome you'll deliver
- The Problem — 2-3 sentences in the customer's words
- What We're Proposing — 3-5 bullet points, concrete deliverables
- Proof — 1-2 customer stories, each with a quantified result
- Investment — pricing line, term, payment shape
- Why Now — the cost of waiting, one specific reason
- Next Step — the single ask, with a date
That's it. If it doesn't fit on one page, cut. The discipline of one page is the point.
Step 4: Visual Design Cues
Recommend:
- A two-column layout (left: problem + proposed solution; right: proof + pricing + next step)
- One visual element (chart, before/after, ROI summary)
- Brand color accents — but keep it readable in B&W in case it's printed
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.
- 1mo ago First seen · 119 lines · 80 tokens per session scan A e76537648378
one-pager is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 23d ago), licensed MIT. It adds 80 tokens to every session and 1,121 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-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.