Automated summary
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 you want to quickly check your MCP connection status or review your Apify spending.
If you need detailed cost analysis or advanced session management.
Security analysis
SafeThe 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
How this analysis is madeExamples
Show me my current Apify MCP sessions.What are my recent Apify actor run costs?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 everycall-actor --jsoncall. 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-mcpcskill README.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/apify-status-and-cost-history-mm8o522g' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/apify-status-and-cost-history-mm8o522g/download' --output '.skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md.part' && mv '.skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md.part' '.skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(mcpc *), Bash(tail *), Bash(awk *)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md' && test -s '.skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/apify-status' && cp -R '.skill-downloads/apify-status-and-cost-history-mm8o522g' '.claude/skills/apify-status'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/apify-status-and-cost-history-mm8o522g'openskills read 'apify-status-and-cost-history-mm8o522g'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/apify-status-and-cost-history-mm8o522g/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.