Skip to main content
skill CX Codex

lindy-cost-tuning — Claude Code skill: what it does, how to install

lindy-cost-tuning audits Lindy AI credit usage, downsizes models, and consolidates agent workflows to cut monthly spending.

MIT 1 installs ★ 2,935 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-cost-tuning -a claude-code
Open on GitHub

What lindy-cost-tuning does

This skill guides you through evaluating Lindy AI workspaces to rein in credit burn. Lindy charges credits per execution step: 1–2 credits on entry models like Gemini Flash up to 10 or more on Claude Opus and outbound phone calls. The workflow walks through auditing task history over the previous 30 days to spot where credits drain fastest.

Savings come from moving simple routing or extraction to smaller LLMs, tightening trigger filters, and merging single-purpose bots into unified chains. It also sets up review thresholds at 50%, 80%, and 95% of the monthly credit allotment. You need billing rights and dashboard task history access in Lindy to gather the necessary data.

What it helps with

  • audit Lindy credit consumption across active agents over 30 days
  • replace oversized models with Gemini Flash or GPT-4o-mini on simple tasks
  • filter email and webhook triggers to stop unnecessary runs
  • merge several single-purpose agents into a consolidated workflow

Example prompts for the agent

  • Audit my Lindy AI credit spend and point out downgrade candidates.
  • Help me consolidate multiple single-task Lindy agents into one workflow.
  • Check my trigger settings to cut down wasted runs on incoming emails.

How to install lindy-cost-tuning

1Skills CLI (Vercel)

npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-cost-tuning -a claude-code

2Manually: put the files in place

~/.claude/skills/lindy-cost-tuning/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/lindy-cost-tuning/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about lindy-cost-tuning

How do I install lindy-cost-tuning in Claude Code?

Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-cost-tuning -a claude-code in your terminal.

What does lindy-cost-tuning do?

It outlines a step-by-step audit process to reduce Lindy AI costs by rightsizing models, filtering triggers, consolidating duplicate agents, and tracking credit quotas.

What prerequisites are needed for this skill?

You need workspace billing access in Lindy, active agents to review, and dashboard permissions to inspect per-agent task logs.

Source text

SKILL.md · MIT
---
name: lindy-cost-tuning
description: 'Optimize Lindy AI costs through credit management, model selection,

  and agent consolidation.

  Use when reducing spend, analyzing credit usage patterns,

  or optimizing budget allocation across agents.

  Trigger with phrases like "lindy cost", "lindy billing",

  "reduce lindy spend", "lindy budget", "lindy credits".

  '
allowed-tools: Read, Write, Edit
version: 1.20.0
license: MIT
author: Jeremy Longshore <[email protected]>
tags:
- saas
- lindy
- cost-optimization
compatibility: Designed for Claude Code
---
# Lindy Cost Tuning

## Overview

Lindy uses a credit-based pricing model. Every task costs credits based on model
size, step count, premium actions, and duration. Cost tuning targets: model
right-sizing, agent consolidation, trigger optimization, and credit monitoring.

## Prerequisites

- Lindy workspace with billing access
- Multiple active agents to evaluate
- Dashboard access to review per-agent task history

## Credit Cost Reference

| Factor | Credits |
|--------|---------|
| Basic model task (Gemini Flash) | 1-2 |
| Mid-tier model (GPT-4o-mini, Claude Haiku) | 2-5 |
| Large model task (GPT-4, Claude Sonnet) | 5-10 |
| Premium model (Claude Opus) | ~10+ |
| Phone call (US/Canada) | ~20/minute |
| Phone call (international) | 21-53/minute |
| Premium actions (webhooks) | Additional per action |
| Minimum per task | 1 credit |

## Plan Costs

| Plan | Monthly | Credits | Per Extra Seat |
|------|---------|---------|----------------|
| Free | $0 | 400 | N/A |
| Pro | $49.99 | 5,000 | $19.99 |
| Business | $299.99 | 30,000 | Included |
| Enterprise | Custom | Custom | Custom |

## Instructions

### Step 1: Audit Agent Credit Consumption

For each active agent, collect:

1. **Task count** (last 30 days) — from Tasks tab
2. **Average credits per task** — total credits / task count
3. **Model used** — from agent settings
4. **Trigger frequency** — how often the agent fires

Create a cost audit table:

| Agent | Tasks/Month | Credits/Task | Model | Monthly Credits | % of Total |
|-------|------------|-------------|-------|----------------|-----------|
| Support Bot | 500 | 5 | Claude Sonnet | 2,500 | 50% |
| Lead Router | 200 | 2 | GPT-4o-mini | 400 | 8% |
| Report Gen | 30 | 10 | GPT-4 | 300 | 6% |

### Step 2: Right-Size Models

The highest-impact optimization. For each agent, ask:
> "Does this task actually need GPT-4/Claude, or would Gemini Flash work?"

| Current Setup | Optimized | Savings |
|--------------|-----------|---------|
| Email classify with Claude Sonnet (5 cr) | Gemini Flash (1 cr) | 80% |
| Data extract with GPT-4 (10 cr) | GPT-4o-mini (3 cr) | 70% |
| Simple routing with Claude Opus (10 cr) | Gemini Flash (1 cr) | 90% |

**Test the downgrade**: Run 10 tasks with the smaller model. Compare output quality.
Most classification, routing, and extraction tasks work identically on smaller models.

### Step 3: Consolidate Redundant Agents

Multiple single-purpose agents cost more than one multi-purpose agent:

Before (5 agents, 5 minimum credits per run):

```
Agent 1: Classify billing emails
Agent 2: Classify technical emails
Agent 3: Classify general emails
Agent 4: Draft billing responses
Agent 5: Draft technical responses
```

After (1 agent, 1 minimum credit per run):

```
Support Agent: Classify email → Condition (billing/technical/general)
  → Draft appropriate response → Send
```

**Cost impact**: Reducing from 5 agents to 1 saves minimum-credit overhead and
simplifies management.

### Step 4: Optimize Trigger Frequency

Credits are consumed every time a trigger fires. Reduce unnecessary triggers:

**Email Received**:

```
Before: Trigger on ALL emails (300/day) = 300 tasks
After:  Filter: label "support" AND NOT from "noreply@" (40/day) = 40 tasks
Savings: 87% fewer tasks
```

**Schedule trigger**:

```
Before: Every 15 minutes (96/day)
After:  Every 2 hours (12/day)
Question: Does this agent really need to run every 15 minutes?
```

**Slack trigger**:

```
Before: Any message in #general (200/day)
After:  Messages containing "@support-bot" (10/day)
Savings: 95% fewer tasks
```

### Step 5: Reduce Steps Per Task

Each action in a workflow costs credits. Eliminate unnecessary steps:

- Combine multiple LLM calls into one (see `lindy-performance-tuning`)
- Use Set Manually instead of AI Prompt for known values
- Remove debug/logging steps in production
- Simplify condition branches

### Step 6: Optimize Knowledge Base Usage

KB search costs credits per query. Optimize:

- Reduce Max Results from 10 to 4 (sufficient for most queries)
- Use specific query instructions to get relevant results in one search
- For small datasets (<100 entries), consider putting data directly in the prompt

### Step 7: Budget Monitoring Setup

1. Check credit usage weekly in **Settings > Billing**
2. Set internal alerts for high-consumption agents:
   - 50% of budget: Warning — review usage
   - 80% of budget: Alert — optimize or upgrade
   - 95% of budget: Critical — pause non-essential agents

### Step 8: Deactivate Idle Agents

Review agents monthly:

- No tasks in 30 days → Pause the agent
- No tasks in 90 days → Delete or archive
- Lindy only charges for active agent execution, not idle agents

## Monthly Cost Optimization Checklist

- [ ] Review per-agent credit consumption
- [ ] Identify agents using large models for simple tasks
- [ ] Check for redundant agents that could be consolidated
- [ ] Review trigger filter effectiveness
- [ ] Remove unused integrations from agents
- [ ] Verify no loops or runaway agent steps
- [ ] Compare actual spend to budget

## Error Handling

| Issue | Cause | Solution |
|-------|-------|----------|
| Unexpected credit spike | Trigger filter removed or loosened | Review and restore trigger filters |
| Agent consuming 10x normal | Looping agent step | Add exit conditions, check task history |
| Credits exhausted mid-month | Under-budgeted or spike | Upgrade plan or pause non-critical agents |
| Model downgrade hurts quality | Task needs larger model | Selectively upgrade only that step |

## Output

Produce a cost-control report showing the workload volume, credit-consuming
steps, monthly budget, proposed optimization, and the expected service-quality
effect. Measure before and after the change rather than inferring savings from
agent configuration alone.

## Examples

For a high-volume enrichment agent, move deterministic validation ahead of the
credit-consuming enrichment step and test it against a representative week of
events. Compare completed useful actions, skipped invalid inputs, and credits
per successful outcome before deploying the new ordering.

## Resources

- [Lindy Pricing](https://www.lindy.ai/pricing)
- [Lindy Documentation](https://docs.lindy.ai)

## Next Steps

Proceed to `lindy-reference-architecture` for production architecture patterns.

© Jeremy Longshore · MIT · jeremylongshore/tons-of-skills-marketplace

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set139

The whole set →
twinmind-cost-tuning twinmind-cost-tuning picks a TwinMind tier and tracks where meeting minutes go. Handy when transcription costs climb and you need a clear picture. CX Codex +1 1installs openevidence-cost-tuning openevidence-cost-tuning evaluates OpenEvidence adoption and workflow burden in healthcare without inventing pricing, quotas, or telemetry. Helps prepare renewal briefs. CX Codex +1 1installs deepgram-cost-tuning The deepgram-cost-tuning skill outlines ways to track Deepgram spend, set budget checks for transcription, and reduce billable audio time through preprocessing. CX Codex +1 1installs clerk-cost-tuning clerk-cost-tuning — a skill that makes Clerk's MRU pricing concrete and trims the bill: auth only where it is needed, caching around the Backend API, a script for idle accounts. CX Codex +1 1installs evernote-cost-tuning The evernote-cost-tuning skill helps track Evernote upload quotas, estimate note sizes, and spot storage-heavy notes. Use it when an integration needs quota checks before uploading attachments. CX Codex +1 1installs posthog-cost-tuning posthog-cost-tuning is a Claude Code skill for PostHog cost analysis: it measures which products drive the bill and trims capture noise without losing events needed for decisions. CX Codex +1 1installs ideogram-cost-tuning ideogram-cost-tuning controls prepaid Ideogram API consumption with admission ceilings, retry limits, and output tracking. Helps teams eliminate wasted spend on failed or duplicate runs. CX Codex +1 1installs coderabbit-cost-tuning The coderabbit-cost-tuning skill reviews CodeRabbit plans, seats, limits, and usage against current billing evidence. Use it to prepare cost scenarios before anyone approves a change. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open