More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    💸 LLM Cost Leak Linter

    2

    The problem LLM application code often contains hidden patterns that drain budgets before billing alerts trigger.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    💸 LLM Cost Leak Linter

    💸 LLM Cost Leak Linter

    Example session with this skill installed

    Scan the src directory for potential LLM cost leaks and tell me if I am wasting tokens.

    • Read your context and instructions
    • Compiled the llm cost leak

    Found 3 cost leaks:

    • LCL002 (High): Loop in chains.py:42 calls gpt-4-turbo without a max_retries limit.
    • LCL005 (Med): loaders.ts:12 passes raw file buffer to prompt without truncation.
    • LCL003 (Low): Using gpt-4 for sentiment analysis on line 88; consider gpt-3.5-turbo.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    LLM application code often contains hidden patterns that drain budgets before billing alerts trigger. Developers lack automated ways to detect uncapped generations, expensive models used for trivial tasks, or inefficient prompting patterns during development.

    What it does

    • Scans source files for LLM calls lacking output caps or truncation logic.
    • Identifies model calls inside loops or retry blocks without attempt limits.
    • Flags expensive models used for high-frequency or simple tasks based on model-pricing.json.
    • Detects instances where entire files are injected into prompts without preprocessing.
    • Points out missing token usage logging and cost instrumentation.

    Frameworks & tools

    Supports Python, JavaScript, TypeScript, and React (JSX/TSX). Works with any LLM provider but requires manual updates to pricing reference files.

    Why this beats prompting it yourself

    Generic LLMs often miss specific architectural cost leaks like loop retry logic or missing backoff limits. This skill provides a structured heuristic scan that maps code patterns to specific cost-risk IDs rather than offering vague advice.

    Use cases

    • Pre-production audit of AI features to prevent runaway costs.
    • Reviewing legacy LLM implementations for potential savings.
    • Standardizing cost-conscious coding practices across a team.

    Known limitations

    This is a heuristic linter, not a runtime monitor. It identifies risky patterns but does not track real-world token usage or live expenditure.

    Heuristic. It flags cost-risk patterns for you to review. It does not measure your actual spend, count live tokens, or run your code, and it cannot confirm a fix works end to end. The expensive-model and cache checks are advisory. The model tiers and prices are only as current as the editable model-pricing.json you maintain. It reads code and structure, not runtime behavior.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 months ago

    Permissions

    Read Files

    File Scopes

    **/.py
    **/.js
    **/.ts
    **/.jsx
    **/.tsx
    **/.mjs

    This skill needs Read Files only. It reads your source files to scan for cost-leak patterns, and reads its own references/model-pricing.json for the model tiers. Findings are returned as text in the conversation. It does not write to disk, run shell commands, make network calls, or read environment variables or secrets.

    Listed4 months ago

    What's inside

    Frequently Asked Questions

    The linter performs a static scan of your codebase to identify patterns like missing 'max_tokens' parameters, model calls inside infinite loops, and instances where high-cost models are used for simple tasks like classification.

    This skill is designed for AI agents with file-system access, such as AutoGPT, Replit Agent, or custom GitHub Action agents. It works by analyzing source files in Python, JavaScript, and TypeScript without requiring execution of the code.

    Since the linter is read-only and performs static analysis, you do not need to provide any API keys or live production credentials for it to scan your logic and identify risks.

    You receive the linter skill logic and a customizable `model-pricing.json` file, allowing you to manually update token prices as providers change their rates or as you gain access to new models.

    No, this is a static analysis tool that flags risky code patterns during development; it does not monitor your live production traffic or provide real-time billing dashboards.

    Every scan generates a plain-English report that identifies the specific file and line number of the risk, explains why it’s a cost hazard, and suggests a more efficient coding pattern.

    New in Code Quality & Review