Stats
Actions
Tags
From apify-mcpc
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/apify-mcpc:apify-statusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the following commands and present the results to the user.
Run the following commands and present the results to the user.
Current mcpc sessions (shows which MCP servers are connected):
mcpc
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.
~/.apify-costs.log — auto-populated by a PostToolUse hook on every call-actor --json call. Override path with $APIFY_COST_LOG.mcpc mcp.apify.com connect @apify. If sessions are missing, run the setup commands from the /apify-mcpc skill README.npx claudepluginhub chocholous/apify-mcpc --plugin apify-mcpcOptimizes Apify Actor costs via compute unit analysis, memory tuning, proxy budgeting, and usage monitoring scripts.
Guides the agent through running Apify web scraping Actors via CLI, MCP, or client, including Actor selection, input schema, execution, and result delivery.
Develop, debug, and deploy Apify Actors — serverless cloud programs for web scraping, automation, and data processing. Guides setup, template selection, and CLI usage.