Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Agent Cost Quick Audit

    1

    Turn your agent logs into a cost table, then separate necessary spend from waste you can delete this week.

    Free

    Security scanned
    Agent Cost Quick Audit

    Agent Cost Quick Audit

    Example session with this skill installed

    Audit my document extraction agent. It processed 100 tasks, cost $12.50, and 15% of requests are retries due to tool loops. The 'summarize' step uses 80% of tokens.

    • Read your context and instructions
    • Compiled the agent cost quick

    I have analyzed the provided logs for the document extraction agent. The primary cost driver is a high input:output ratio in the summarization phase, compounded by tool loop inefficiencies.

    Agent cost audit — Document Extraction — Current Batch

    Sample: 100 requests · Total: $12.50 · Cost per successful task: $0.15

    Where the money goes

    StepShare of spendBucketWhy
    Summarize80%Structural WasteFull document re-sent for each summary turn instead of using snippets.
    Verification15%Loop WasteTool loops causing 15% retry rate on extraction validation.
    Routing5%Model WasteUsing frontier model for simple classification of document types.

    Waste found

    ItemEst. monthly savingConfidenceChangeRisk to quality
    Context Capping$4.00HighSend only relevant chunks to 'Summarize' step.Low
    Loop Detection$1.80HighImplement step cap and detect identical tool calls.None
    Model Swap$0.50MediumRoute 'Routing' step to a smaller, cheaper model.Low

    Do not touch

    The initial ingestion step is necessary as the full text must be parsed at least once to ensure extraction accuracy.

    Measurement plan

    Baseline: $0.15 per successful task → implement context capping → re-measure on 100 tasks using the standard extraction eval set.

    Next steps

    1. Implement a tool loop detection check to break identical call cycles.
    2. Update the 'Summarize' prompt to accept retrieved chunks instead of the full document string.
    3. Compare extraction accuracy on the smaller model for the routing step.

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

    About this skill

    Generic cost advice ("shorten prompts, use a smaller model") rarely survives contact with a real bill. This audit answers a narrower question from your own data: which part of the pipeline is spending, and how much of it is waste?

    What you get

    • A cost table built from 50-100 real requests: feature, step, model, input, output, retries, cost.
    • A four-bucket classification - necessary, structural waste, loop waste, model waste - because each one needs a different fix.
    • The five baseline numbers worth knowing, including cost per successful task and the retry share of spend.
    • Seven cheap wins to do before anything clever, and a report format with arithmetic behind every saving.

    How it works

    Group spend by the dimension you control. Two or three steps usually carry most of the bill; find those, classify them, then change one thing and re-measure on the same tasks.

    Who it is for

    Teams whose agent margin is thinner than expected, or who have just been asked why a feature costs so much per task.

    Limits

    Token counts are not the whole bill, and this cannot tell you whether quality dropped after a change - you need even a small eval set for that.

    Free starter. For per-step attribution in multi-agent systems, a waste taxonomy with detection queries, routing simulations with quality checks and prompt-cache design, see Agent Cost Profiler: https://www.agensi.io/skills/agent-cost-profiler

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Requires existing logs with token counts and retry data. Cannot measure quality regressions; requires a separate eval set to verify optimizations.

    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 buying a skill.

    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

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    • Free with an Agensi account

    Requires

    Nothing to install.

    Permissions

    No special permissions declared or detected

    Listed2 days ago

    What's inside

    Frequently Asked Questions

    This skill is model-agnostic and works with logs from any provider that uses token-based pricing, including OpenAI, Anthropic, and Gemini. It is designed to audit any agentic architecture, whether built with LangChain, AutoGPT, or custom frameworks.

    You will receive a comprehensive audit framework, a structured data template for cost attribution, and a standardized reporting markdown template to present findings to stakeholders. It also includes the logic for classifying token waste and calculating cost-per-success metrics.

    Unlike generic cost-saving tips, this skill specifically targets 'agentic waste' like redundant tool loops and unoptimized history handling. It ensures you don't sacrifice output quality by prematurely switching to a smaller model when the real issue is structural inefficiency.

    Implementation is straightforward; you simply need to gather request logs (input/output tokens, latency, and retries) for 50-100 recent tasks. The skill then provides the structured methodology to process this data into an actionable optimization roadmap.

    While the audit identifies where tokens are being wasted, any changes to your agent’s logic or prompts should be verified with your existing evaluation suite. The skill includes a 'quality risk assessment' section in the report to help you track these potential impacts.

    New in LLM Ops

    Free