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.
npx skills add aAAaqwq/AGI-Super-Team --skill amplitude-automationgit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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.
[](https://agentmods.dev/skills/aaaaqwq/agi-super-team/amplitude-automation)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/amplitude-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/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.
<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/amplitude-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/amplitude-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.01916 |
| Opus 5 | $0.00018 | $0.00958 |
| Sonnet 5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00192 |
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 12d 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.
This is a copy
97% identical to amplitude-automation — 13 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.
How it starts
The opening of the file, as written. The whole thing — 217 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_CONNECTIONSwith toolkitamplitude - Always call
RUBE_SEARCH_TOOLSfirst 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitamplitude - If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication
- 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:
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 nodevice_id)device_id: Device identifier (required if nouser_id)event_properties: Object with custom event propertiesuser_properties: Object with user properties to settime: Event timestamp in milliseconds since epoch
Pitfalls:
- At least one of
user_idordevice_idis required per event event_typeis required for every event; cannot be emptytimemust 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:
AMPLITUDE_FIND_USER- Find user by ID or property [Prerequisite]AMPLITUDE_GET_USER_ACTIVITY- Retrieve user's event stream [Required]
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.
- 12d ago First seen · 217 lines · 37 tokens per session scan A 45fb403deecf
amplitude-automation is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (92 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,916 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to amplitude-automation, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
guidance
Add, edit, or audit guidance docs. Default writes guidance for Claude (.claude/guidance/, Markdown, moflo universal rules). -h writes for human readers (docs/, lighter ruleset). --html emits HTML with a minimal default stylesheet instead of Markdown. -a audits the .claude/guidance/ directory.
deslop
The optimization pass, defined - delete before you add, one smell class per pass, behaviour pinned by a test that ran BEFORE the edit. Lints a SKILL.md and prose by the same instinct. Use for the per-story optimization pass or when code has grown noisy without growing capable.
eldar
Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance…
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
memory-worktree
Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my…
code-tour
Maintain docs/code-tour.md — the annotated guided reading of Aigon's core logic. Use when you have changed code the tour quotes, added a subsystem a new reader would need, or the user says "update the code tour", "the tour is stale", "add X to the code tour", or asks to review/refresh the code examples doc.