Skills Guide

Apify Status and Cost History

VerifiedSafe

Displays active Apify/mcpc sessions and recent run cost history. Use this skill when you need to check connected MCP servers, review actor execution costs, or see which actors have been called recently.

Sby Skills Guide Bot
DevelopmentBeginner
706/2/2026
Claude Code
#apify#mcpc#cost-tracking#session-status

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Shows current Apify MCP session state and recent actor run cost history.

Strengths

  • Quick overview of active MCP sessions.
  • Tracks cumulative costs of actor executions.
  • Uses simple bash commands with no manual setup required.

Limitations

  • Relies on the ~/.apify-costs.log file which must exist.
  • Only works with sessions managed via mcpc.
  • Cost history limited to the last 20 entries.
When to use it

When you want to quickly check your MCP connection status or review your Apify spending.

When not to use it

If you need detailed cost analysis or advanced session management.

Security analysis

Safe
Quality score90/100

The skill only executes read-only commands (mcpc, tail, awk) on local files to display session info and cost history. No destructive or exfiltration actions are present.

No concerns found

Examples

Check current sessions
Show me my current Apify MCP sessions.
View cost history
What are my recent Apify actor run costs?
Full status overview
Show me the Apify status including sessions and costs.

name: apify-status description: "Shows current Apify/mcpc session state and run cost history. Use when the user asks about their Apify usage, mcpc session status, costs, or wants to see what actors were run recently." allowed-tools: Bash(mcpc *), Bash(tail *), Bash(awk *) argument-hint: "[sessions | costs | all]"

apify-status

Run the following commands and present the results to the user.

Sessions

Current mcpc sessions (shows which MCP servers are connected):

mcpc

Cost history

Recent actor runs (last 20 entries from cost log):

tail -n 20 ~/.apify-costs.log

Total spend across all logged runs:

awk -F'\t' '{match($0,/usd=([0-9.]+)/,a); sum+=a[1]} END{printf "Total: $%.4f USD\n", sum}' ~/.apify-costs.log

If either cost command fails (file not found), inform the user that cost tracking starts automatically once they run an actor with call-actor ... --json. No manual setup needed.

Notes

  • Cost log: ~/.apify-costs.log — auto-populated by a PostToolUse hook on every call-actor --json call. Override path with $APIFY_COST_LOG.
  • Sessions: managed via mcpc mcp.apify.com connect @apify. If sessions are missing, run the setup commands from the /apify-mcpc skill README.
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,848
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
822
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
683
Admin