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 oyi77/1ai-skills --skill revenue-enginegit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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/oyi77/1ai-skills/revenue-engine)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/revenue-engine"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/revenue-engine/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/oyi77/1ai-skills/revenue-engine"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/revenue-engine.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.00031 | $0.01276 |
| Opus 5 | $0.00015 | $0.00638 |
| Sonnet 5 | $0.00006 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade C, and why
revenue-engine scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
echo "MRR: $(curl -s https://api.stripe.com/v1/subscriptions --header "Authorization: Bearer $STRIPE_KEY" 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); print(sum(int(i['plan']['amount']) for i in d[' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
echo "MRR: $(curl -s https://api.stripe.com/v1/subscriptions --header "Authorization: Bearer $STRIPE_KEY" 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); print(sum(int(i['plan']['amount']) for i in d[' How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill manages revenue pipelines end to end: tracking Stripe and analytics metrics, and automating financial reporting for SaaS businesses. Use it when money metrics must be visible and attributable. It wires the measurement loop from raw events to the reports you act on.
Money-Making Overview
This engine is the financial nervous system of your business. Without it, you leak 5-15% of revenue through forgotten invoices, missed renewals, and untracked metrics. With it, you capture every dollar and know exactly where to focus to grow.
Dependencies
- Python 3.8+ or Node.js 18+
- Access to relevant APIs/services for your specific use case
- Basic understanding of the domain concepts
Commands
# Refer to the skill's usage section for specific commands
# Adapt these to your workflow
Revenue Streams
- Your Own Revenue Ops — tracking prevents leakage
- Revenue Dashboard Service ($2K-5K/setup) — build for clients
- CFO-as-a-Service ($1K-3K/mo) — ongoing financial monitoring
First Action in 60 Minutes
#!/usr/bin/env bash
# Revenue engine health check
mkdir -p ~/revenue-engine/{metrics,reports,alerts}
echo "=== Revenue Health Check ==="
echo "MRR: $(curl -s https://api.stripe.com/v1/subscriptions --header "Authorization: Bearer $STRIPE_KEY" 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); print(sum(int(i['plan']['amount']) for i in d['data'])/100)" 2>/dev/null || echo 'Set \$STRIPE_KEY')"
echo ""
echo "Metrics to track this week:"
echo " - MRR growth rate"
echo " - Churn rate (exits / total)"
echo " - LTV (avg revenue × avg months retained)"
echo " - CAC (total sales cost / new customers)"
echo " - Quick Ratio (new MRR + expansion MRR) / churned MRR"
Revenue Pipeline Architecture
Revenue Engine is a foundational core infrastructure skill that provides system foundation capabilities for the agent ecosystem.
- Input layer — Receives and validates incoming requests
- Processing layer — Core logic for system foundation
- Output layer — Formats and delivers results
- State management — Maintains context across invocations
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.
- yesterday Changed · +11 lines f8c97e5e7b66
- 8d ago First seen · 151 lines · 31 tokens per session scan C 953a663e26e4
revenue-engine is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,276 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
cost-efficiency-analyzer
Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…
multi-quarter-trend-analysis
Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for "how are we trending", "show me the trend", "track performance over time", "quarter over quarter…
executive-financial-briefing
Generates a concise executive-level financial briefing or summary suitable for a CEO, CFO, or board presentation. Use when the user asks for a summary, briefing, executive summary, board update, financial overview, financial health check, or "how is the business doing". Covers the full P&L picture in one page. Also…
quarterly-kpi-calculator
Calculates quarterly financial KPIs from P&L data. P&L figures can be provided directly by the user or fetched from the financial data MCP server. Use when the user wants KPI calculations such as Gross Margin %, EBITDA Margin %, Operating Expense Ratio, or Revenue Growth % QoQ. Also use for quarterly performance…
revenue-growth-analyst
Deep-dives into revenue growth patterns, growth rates, and growth quality. Use when the user asks specifically about revenue growth, top-line performance, sales growth, revenue acceleration or deceleration, growth trajectory, or wants to understand what is driving revenue changes. NOT for cost or margin analysis …
portfolio-risk
Assess the risk profile of a set of stocks or a sector allocation, scoring concentration risk, volatility exposure, and overall risk tier.