amplitude-automation

amplitude-automation is a skill for Claude Code, Codex from henryalouf/ruflow. It costs 37 tokens per session (1,945 once invoked), scanned A, a copy of amplitude-automation, MIT.

A set of workflows for automating Amplitude, a product-analytics service that records how people use an app. It covers sending events, identifying users, viewing activity, and working with cohorts through connected tools.

In plain words
What is it for?
Use it to send events such as sign-ups or purchases, identify users, inspect user activity, and manage or analyze cohorts.
Why use it?
It reduces manual work when keeping product-usage data up to date or investigating user behavior. The source requires a connected Rube MCP service and an active Amplitude connection.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to send events such as sign-ups or purchases, identify users, inspect user activity, and manage or analyze cohorts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/henryalouf/ruflow/amplitude-automation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add henryalouf/ruflow --skill amplitude-automation
Clone the repo
git clone --depth 1 https://github.com/henryalouf/ruflow

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for amplitude-automation

README.md
[![agentmods](https://agentmods.dev/badge/skills/henryalouf/ruflow/amplitude-automation/github.svg)](https://agentmods.dev/skills/henryalouf/ruflow/amplitude-automation)
Your own site
<a href="https://agentmods.dev/skills/henryalouf/ruflow/amplitude-automation"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/amplitude-automation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for amplitude-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/henryalouf/ruflow/amplitude-automation"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/amplitude-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,945 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.01945
Opus 5 $0.00018 $0.00972
Sonnet 5 $0.00007 $0.00389
Haiku 4.5 $0.00004 $0.00194

Measured 9d ago against content hash 33e0dd4c5c5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

amplitude-automation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to amplitude-automation — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/amplitude-automation/SKILL.md · 221 lines

How it starts

The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Amplitude Automation via Rube MCP

Automate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Amplitude connection via RUBE_MANAGE_CONNECTIONS with toolkit amplitude
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit amplitude
  3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication
  4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Send Events

When to use: User wants to track events or send event data to Amplitude

Tool sequence:

  1. AMPLITUDE_SEND_EVENTS - Send one or more events to Amplitude [Required]

Key parameters:

  • events: Array of event objects, each containing:
    • event_type: Name of the event (e.g., 'page_view', 'purchase')
    • user_id: Unique user identifier (required if no device_id)
    • device_id: Device identifier (required if no user_id)
    • event_properties: Object with custom event properties
    • user_properties: Object with user properties to set
    • time: Event timestamp in milliseconds since epoch

Pitfalls:

  • At least one of user_id or device_id is required per event
  • event_type is required for every event; cannot be empty
  • time must be in milliseconds (13-digit epoch), not seconds
  • Batch limit applies; check schema for maximum events per request
  • Events are processed asynchronously; successful API response does not mean data is immediately queryable

2. Get User Activity

When to use: User wants to view event history for a specific user

Tool sequence:

  1. AMPLITUDE_FIND_USER - Find user by ID or property [Prerequisite]
  2. AMPLITUDE_GET_USER_ACTIVITY - Retrieve user's event stream [Required]

Read the full file on GitHub · 221 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 221 lines · 37 tokens per session scan A 33e0dd4c5c5c

Subscribe to this mod's changes

amplitude-automation is a skill published in the GitHub repository henryalouf/ruflow (129 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,945 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to amplitude-automation, differing in 5 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens