revenue-pulse

revenue-pulse is a skill for Claude Code, Codex from elie222/atom-eve. It costs 33 tokens per session (880 once invoked), scanned A, original, MIT.

A weekly reporting workflow for Stripe revenue and customer cancellations, with supporting product-usage data from PostHog. Stripe handles payments and subscriptions; churn means customers or subscriptions being lost.

In plain words
What is it for?
Use it to prepare a weekly revenue-and-churn update for Slack, covering subscription activity, cancellations, failed payments, and possible payment or retention problems.
Why use it?
It replaces guesses with figures pulled from the relevant command-line tools, including new subscriptions, cancellations, failed payments, and accounts at risk.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a weekly revenue-and-churn update for Slack, covering subscription activity, cancellations, failed payments, and possible payment or retention problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/elie222/atom-eve/revenue-pulse
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 elie222/atom-eve --skill revenue-pulse
Clone the repo
git clone --depth 1 https://github.com/elie222/atom-eve

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 revenue-pulse

README.md
[![agentmods](https://agentmods.dev/badge/skills/elie222/atom-eve/revenue-pulse/github.svg)](https://agentmods.dev/skills/elie222/atom-eve/revenue-pulse)
Your own site
<a href="https://agentmods.dev/skills/elie222/atom-eve/revenue-pulse"><img src="https://agentmods.dev/badge/skills/elie222/atom-eve/revenue-pulse/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 revenue-pulse

Your own site · 80×15
<a href="https://agentmods.dev/skills/elie222/atom-eve/revenue-pulse"><img src="https://agentmods.dev/badge/skills/elie222/atom-eve/revenue-pulse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 880 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 original No closer match found 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.00033 $0.00880
Opus 5 $0.00016 $0.00440
Sonnet 5 $0.00007 $0.00176
Haiku 4.5 $0.00003 $0.00088

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

Security

Grade A, and why

revenue-pulse 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.

registry/stripe-pulse/agent/skills/revenue-pulse/SKILL.md · 101 lines

How it starts

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

Revenue & churn pulse workflow

You produce a grounded weekly revenue & churn pulse. All numbers come from CLIs you run in the sandbox with bash. Never invent a figure.

0. Window

Compute the lookback window in Unix seconds. Default 7 days:

UNTIL=$(date +%s); SINCE=$(( UNTIL - 7*86400 ))

1. Stripe facts (stripe CLI)

Auth comes from STRIPE_API_KEY (a restricted, read-only key) in the env. Every command returns JSON — pipe through jq. Add --live for live data (default is test mode). Use --limit and paginate with --starting-after.

  • New / active subscriptions in the window:
    stripe subscriptions list --status active --created "gte=$SINCE" --limit 100
    
  • Cancellations (churn) in the window — read the events, not just current state:
    stripe events list --type "customer.subscription.deleted" --created "gte=$SINCE" --limit 100
    
  • Failed payments / dunning risk:
    stripe invoices list --status open --created "gte=$SINCE" --limit 100
    stripe events list --type "invoice.payment_failed" --created "gte=$SINCE" --limit 100
    
  • At-risk subscriptions (set to cancel, or past_due):
    stripe subscriptions list --status past_due --limit 100
    stripe get /v1/subscriptions -d "status=active" -d "limit=100" \
      | jq '.data[] | select(.cancel_at_period_end == true)'
    

MRR: derive it from the subscription items' recurring prices (items.data[].price.unit_amount * quantity, normalized to monthly). Sum across active subscriptions; do not guess. Compare against the prior window the same way.

stripe get / stripe post give raw API access for anything a resource sub-command doesn't surface directly.

2. Engagement cross-reference (posthog-cli)

For each at-risk customer, check product engagement. Auth via POSTHOG_CLI_API_KEY and POSTHOG_CLI_PROJECT_ID.

Use the posthog-cli api workflow. Do not guess tool names or schemas:

posthog-cli api search query
posthog-cli api info <tool>
posthog-cli api call read-data-schema '<json>'
posthog-cli api call <tool> '<json>'

Read the full file on GitHub · 101 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. 12d ago First seen · 101 lines · 33 tokens per session scan A 4892177cc033

Subscribe to this mod's changes

revenue-pulse is a skill published in the GitHub repository elie222/atom-eve (49 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 880 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.