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 octavehq/lfgtm --skill champion-deal-roomgit clone --depth 1 https://github.com/octavehq/lfgtmWrote 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/octavehq/lfgtm/champion-deal-room)<a href="https://agentmods.dev/skills/octavehq/lfgtm/champion-deal-room"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/champion-deal-room/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/octavehq/lfgtm/champion-deal-room"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/champion-deal-room.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.00127 | $0.05241 |
| Opus 5 | $0.00063 | $0.02620 |
| Sonnet 5 | $0.00025 | $0.01048 |
| Haiku 4.5 | $0.00013 | $0.00524 |
Grade A, and why
champion-deal-room 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 12d 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/octave:champion-deal-room - Champion Deal Room
Generate a dense, self-contained HTML deal room that a rep hands to an internal champion so the champion can run the buying-committee sell without the rep in the room.
The mental model: your champion believes, but they now have to convince a CFO, an IT lead, an auditor, and a security engineer who were not on your calls. This is the working document they run that sell from. It is not a pitch and it is not pretty for its own sake. It is facts and ammunition: the number, the map of who must say yes, the exact thing each person needs to hear, the answers to the hard questions, and the path to signature.
This is a working document, not a landing page. Dense, scannable, information-first, in the meeting-prep battle-plan style (collapsible sections, sidebar nav, real card vocabulary). The champion opens it to prepare for an internal meeting and to forward pieces to colleagues. Every section must carry a fact, not a talking point.
How this differs from other skills:
- vs
/octave:microsite— that is a customer-facing, top-of-funnel attention grabber for a cold reader. This is an internal, mid-to-late-deal working kit for a reader who already believes. - vs
/octave:proposal— proposal is the polished vendor document addressed to the buyer's execs, the formal closing artifact. This is the champion's candid internal kit organized around the committee and the path to consensus, the thing that gets a deal to the point where a proposal lands. - vs
/octave:abm— abm is the rep's account plan (how the rep pursues the account). This is written for the champion, in service of the champion's internal sell. - vs
/octave:meeting-prep— meeting-prep coaches your rep for one meeting. This coaches the champion for the meetings you are not in.
The six jobs
Six jobs, one section each. Nothing else earns a place. Each answers a question the champion has to answer for their org when you are not in the room.
- The case for change — the problem in their words, why now, and the one-line version that survives being repeated by people who were not on the calls. The champion carries this up the chain, so engineer it to travel: give them the sentence they say to the board, not just a situation recap. A short verdict up top so a busy reader gets the state of play in five seconds.
- Positioning and value — how to frame the value for the org, with the ROI case where it can be quantified. Reframe value as positioning first, numbers second: the section must work even when hard dollars are not groundable. The numbers come from the offering's own value drivers (derive them, never assume a fixed model), and you prompt the user for the 2-3 inputs that quantify them (see Step 2). Where you do quantify, show the arithmetic and label estimates.
- Who else to bring in (the committee) — the seats beyond the champion that must weigh in, and how to frame it for each. The champion is the reader, not a card here. Data-gated (see below): real names only for people who appear in real deal signals; everyone else is a role to loop in, not an asserted stakeholder.
- Objection handling — the pushback the committee will raise, including the competitive comparison, each answered with a proof anchor.
- Proof and references — the evidence, scaled to their size and industry, that de-risks the decision.
- The path forward — the low-risk next step, the cost of waiting, and the route to a decision.
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.
- 12d ago First seen · 332 lines · 127 tokens per session scan A e363dc031aab
champion-deal-room is a skill published in the GitHub repository octavehq/lfgtm (11 stars, last pushed 22d ago), licensed MIT. It adds 127 tokens to every session and 5,241 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…