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 agentmods add commands/gotempsh/temps/revenuegit clone --depth 1 https://github.com/gotempsh/tempsWrote 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/commands/gotempsh/temps/revenue)<a href="https://agentmods.dev/commands/gotempsh/temps/revenue"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/revenue.svg" alt="Measured on agentmods" 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.00000 | $0.00418 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
revenue 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 2d 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.
What it actually says
revenue command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
revenue
Manage revenue integrations and import historical data
Subcommands:
import- Import historical revenue data from a CSV export
revenue import
Import historical revenue data from a CSV export
Subcommands:
subscriptions- Import current subscriptions CSV (e.g., Stripe → Subscriptions → Export)invoices- Import paid invoices CSV to backfill the revenue chart
revenue import subscriptions
Import current subscriptions CSV (e.g., Stripe → Subscriptions → Export)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <slug> |
Project slug (defaults to linked project) | - | No |
--integration-id <id> |
Target integration ID (auto-detected if only one exists) | - | No |
--provider <name> |
Target provider name (e.g., stripe) | - | No |
--json |
Output the import outcome as JSON (suppresses spinners) | - | No |
revenue import invoices
Import paid invoices CSV to backfill the revenue chart
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --project <slug> |
Project slug (defaults to linked project) | - | No |
--integration-id <id> |
Target integration ID (auto-detected if only one exists) | - | No |
--provider <name> |
Target provider name (e.g., stripe) | - | No |
--json |
Output the import outcome as JSON (suppresses spinners) | - | No |
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.
- 2d ago First seen · 49 lines · 0 tokens per session scan A 9435cdae4615
revenue is a command published in the GitHub repository gotempsh/temps (712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 418 tokens. 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-09-03.
Other commands, from other repositories
pr-check
Run all local CI checks before creating a PR.
ci-health
Check all GitHub Actions workflows for failures, create P0 tickets, gate each ticket, and auto-fix safe failures.
ci-status
Real-time GitHub Actions workflow status and recent runs.
finops-execute
Step 4 (Execution) — convert a Definition-of-Ready plan into a deployed, verified change at an automation level the user picks per opportunity (L1 Manual, L2 Guided, L3 CI/CD, L4 Autonomous). Applies the verification gate: deployed, verified, rollback proven. Mutates.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.