automation-pricing-and-close

automation-pricing-and-close is a skill for Claude Code, Codex from jpeslar1/john-peslar-ai-skills. It costs 46 tokens per session (990 once invoked), scanned A, original, MIT.

A sales guide for pricing a scoped business-automation project and handling the conversation that leads to a decision. It separates one-time setup work from recurring services and uses stated costs and assumptions.

In plain words
What is it for?
Use it to price automation pilots, calculate setup and monthly cost floors, define overages, and prepare closing conversations with buyers.
Why use it?
It helps avoid arbitrary prices, unclear scope, and open-ended support commitments. Missing information is called out instead of being silently guessed.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: positional $N argument.

Part of the sales-101 plugin — 10 skills shipped together

Good fit Use it to price automation pilots, calculate setup and monthly cost floors, define overages, and prepare closing conversations with buyers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close
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.

Any agent
npx skills add jpeslar1/john-peslar-ai-skills --skill automation-pricing-and-close
Clone the repo
git clone --depth 1 https://github.com/jpeslar1/john-peslar-ai-skills

Made for: Claude Code, Codex.

Or install sales-101, the plugin that ships this one along with the rest of its 10 skills.

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 automation-pricing-and-close

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close/github.svg)](https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close)
Your own site
<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close/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 automation-pricing-and-close

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close"><img src="https://agentmods.dev/badge/skills/jpeslar1/john-peslar-ai-skills/automation-pricing-and-close.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 990 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.00046 $0.00990
Opus 5 $0.00023 $0.00495
Sonnet 5 $0.00009 $0.00198
Haiku 4.5 $0.00005 $0.00099

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

Security

Grade A, and why

automation-pricing-and-close 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 3d 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.

automation-pricing-and-close/SKILL.md · 67 lines

How it starts

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

Automation Pricing and Close

Turn a qualified problem into a sustainable price and an explicit decision. Treat all proposed terms as drafts. A first sale should not create unlimited delivery obligations.

Establish scope and economics

Use the buyer's confirmed problem and success metric, included workflow/integrations, delivery effort, subcontractor and platform costs, support load, buyer dependencies, proof, alternatives, and preferred currency. Ask for missing cost assumptions that materially change the price. If no qualified opportunity exists, give provisional pricing with the discovery gaps.

Separate setup work from recurring work. A one-time workflow with no ongoing service does not justify a retainer by itself. Name monitoring, maintenance, usage, reporting, and support inclusions only when the seller will deliver them. Identify overages and change requests.

Calculate, using supplied or explicitly labeled scenario inputs:

  • Delivery cost = labor hours x loaded hourly cost + direct costs + stated contingency.
  • Setup floor at target gross margin = setup cost / (1 - margin).
  • Monthly floor at target gross margin = recurring cost / (1 - margin).

Specify currency, margin as a fraction below 1, and assumptions. Do not confuse margin with markup: a hypothetical cost of $600 at 50% gross margin implies a $1,200 floor, not $900. A floor is not proof of willingness to pay.

Compare the floor with credible buyer value and alternatives. Use buyer-provided baselines for time or cost savings and show the calculation. Treat uncertain savings as a range. Do not price from fabricated ROI or claim that a particular multiple is universally correct.

Recommend a simple price ladder

Present one recommended paid pilot or setup plus retainer, with an optional alternative only if the tradeoff is meaningful. Explain the deliverables, duration, setup fee, recurring fee if any, billing trigger, customer obligations, scope exclusions, and acceptance process. If the affordable budget is below the delivery floor, reduce scope or decline; do not hide losses in an uncapped guarantee.

Read the full file on GitHub · 67 lines

Files

What ships with it

1 file 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.

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. 3d ago First seen · 67 lines · 46 tokens per session scan A d9e62e0cd4e5

Subscribe to this mod's changes

automation-pricing-and-close is a skill published in the GitHub repository jpeslar1/john-peslar-ai-skills (6 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 990 once invoked, about $0.0002 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-09-09.

Related

Other skills, from other repositories

weekly-update

OpenDesign's weekly metrics standup: this week's numbers, the one anomaly, and the single decision it forces. Built as a decision-grade data & finance deck for ops & growth team.

nexu-io/open-design · 41 tokens

close-management

Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.

anthropics/knowledge-work-plugins · 40 tokens

dd-checklist

Generate and track comprehensive due diligence checklists tailored to the target company's sector, deal type, and complexity. Covers all major workstreams with request lists, status tracking, and red flag escalation. Use when kicking off diligence, organizing a data room review, or tracking outstanding items. Triggers…

anthropics/financial-services · 91 tokens

closing-checklist

What's blocking close — maintain the closing checklist with status, critical path, and days to close. Self-updating: ingests new items from diligence findings and schedule builds, tracks status, surfaces what's blocking. Use when user says "closing checklist", "what's left to close", "checklist status", "add to the…

anthropics/claude-for-legal · 78 tokens

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens

Freelance Empire

Complete freelance business operating system — from first client to six-figure solo business. Covers positioning, pricing, proposals, client management, finances, scaling, and the transition from side-hustle to full-time. Use when starting freelancing, raising rates, managing clients, building recurring revenue, or…

LeoYeAI/openclaw-master-skills · 71 tokens