talk-to-deal

talk-to-deal is a command for Claude Code from ololand-ai/ololand-plugins. It costs 25 tokens per session (809 once invoked), scanned A, original, Apache-2.0.

A conversational interface for asking natural-language questions about a deal and receiving concise, voice-friendly answers.

In plain words
What is it for?
Use it for simple lookups and spoken deal check-ins, including questions that may lead to clear recommendations.
Why use it?
It makes quick deal reviews easier when you need an answer rather than a full written analysis.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ololand-dd plugin — 22 skills, 52 commands, 3 agents shipped together

Good fit Use it for simple lookups and spoken deal check-ins, including questions that may lead to clear recommendations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ololand-ai/ololand-plugins/talk-to-deal
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 52 commands, 3 agents.

Wrote 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.

agentmods badge for talk-to-deal

README.md
[![agentmods](https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/talk-to-deal/github.svg)](https://agentmods.dev/commands/ololand-ai/ololand-plugins/talk-to-deal)
Your own site
<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/talk-to-deal"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/talk-to-deal/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.

agentmods 80×15 button for talk-to-deal

Your own site · 80×15
<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/talk-to-deal"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/talk-to-deal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00809
Opus 5 $0.00013 $0.00404
Sonnet 5 $0.00005 $0.00162
Haiku 4.5 $0.00003 $0.00081

Measured 10d ago against content hash bc634f9d0fee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

talk-to-deal 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 10d 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.

plugins/ololand-dd/commands/talk-to-deal.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Talk to Your Deal

Have a natural conversation about a deal. Returns voice-optimized responses suitable for hands-free review, Claude Dispatch, or quick deal check-ins.

Usage

/talk-to-deal <deal_id> <question>

Arguments

  • deal_id (required) — The deal to ask about.
  • question (required) — Natural language question about the deal.

Execution

  1. Classify the request before choosing a rail:
    • For a simple lookup-style question covered by /plan's no-plan exceptions, call talk_to_deal from the MCP server with the deal_id and question.
    • Before every other non-trivial deal question, follow /plan: create or reuse the conversation session, submit the user's verbatim question with submit_plan_for_approval, render the proposed steps, and stop for the user's approval. Never invoke either MCP message tool for that planned execution. After approval, direct the user to continue the same session in the OloLand app or normal SSE/message endpoint with the returned plan payload supplied as approved_plan on SubmitMessageRequest. That field supplies execution context; it is not a persisted or hash-validated approval identity. The MCP talk_to_deal and ask_deal_agent tools cannot carry it, and quoted plan text is not a substitute. If the client cannot use the normal session endpoint, report governed execution as unavailable on this rail.
    • Do not fall back to an MCP message call after planning, even if required_sections=["answer", "evidence", "assumptions", "open_questions"] would otherwise be supported. Completion headings and a read-only boundary do not replace the normal endpoint's approved_plan execution context.
  2. For the lookup-only talk_to_deal path, relay any returned boundary_gate, completion_contract, and grader_passed fields. A response is not a completed or verified answer merely because text was returned. If any applicable field is absent, unavailable, or failed, say so plainly and do not replace it with an inferred pass.
  3. Every deal fact, figure, date, risk, or recommendation must retain its returned inline source citation. Voice style may round a cited number (for example, "about $160 million [3]"), but must not remove its citation or convert missing evidence into an estimate. State unavailable evidence and the resulting limitation instead.
  4. Do not state a buyer's or acquirer's identity, strategy, mandate, interest, expected synergies, or likely action unless it is supported by a tenant-authorized returned source citation. A caller-supplied premise may be discussed only when labeled as a hypothetical, not as a fact about the buyer.
  5. The response uses voice-mode directives:
    • Concise (2-3 sentences per point)
    • Rounded numbers ("about 160 million" not "$164,501,234")
    • Narrative style, no markdown tables
    • Clear recommendation or next question at the end

Read the full file on GitHub · 49 lines

Changes

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.

  1. 10d ago First seen · 49 lines · 25 tokens per session scan A bc634f9d0fee

Subscribe to this mod's changes

talk-to-deal is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 25 tokens to every session and 809 once invoked, about $0.0001 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-31.