lindy-cost-tuning
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". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lindy-cost-tuning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
What does the lindy-cost-tuning skill do?
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". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill lindy-cost-tuning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.