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/fergupa/claude_plugins/income-statementgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/income-statement)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/income-statement"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/income-statement.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 | $0.00012 | $0.01499 |
| Opus 5 | $0.00006 | $0.00749 |
| Sonnet 5 | $0.00002 | $0.00300 |
| Haiku 4.5 | $0.00001 | $0.00150 |
Grade A, and why
income-statement 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Income Statement Generation
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Important: This command assists with financial statement workflows but does not provide financial advice. All statements should be reviewed by qualified financial professionals before use in reporting or filings.
Generate an income statement with period-over-period comparison and variance analysis. Highlight material variances for investigation.
Usage
/income-statement <period-type> <period>
Arguments
period-type— The reporting period type:monthly— Single month P&L with prior month and prior year month comparisonquarterly— Quarter P&L with prior quarter and prior year quarter comparisonannual— Full year P&L with prior year comparisonytd— Year-to-date P&L with prior year YTD comparison
period— The period to report (e.g.,2024-12,2024-Q4,2024)
Workflow
1. Gather Financial Data
If ~~erp or ~~data warehouse is connected:
- Pull trial balance or income statement data for the specified period
- Pull comparison period data (prior period, prior year, budget/forecast)
- Pull account hierarchy and groupings for presentation
If no data source is connected:
Connect ~~erp or ~~data warehouse to pull financial data automatically. You can also paste trial balance data, upload a spreadsheet, or provide income statement data for analysis.
Prompt the user to provide:
- Current period revenue and expense data (by account or category)
- Comparison period data (prior period, prior year, and/or budget)
- Any known adjustments or reclassifications
2. Generate Income Statement
Present in standard multi-column format:
INCOME STATEMENT
Period: [Period description]
(in thousands, unless otherwise noted)
Current Prior Variance Variance Budget Budget
Period Period ($) (%) Amount Var ($)
-------- -------- -------- -------- -------- --------
REVENUE
Product revenue $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
Service revenue $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
Other revenue $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
-------- -------- -------- -------- --------
TOTAL REVENUE $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
COST OF REVENUE
[Cost items] $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
-------- -------- -------- -------- --------
GROSS PROFIT $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
Gross Margin XX.X% XX.X%
OPERATING EXPENSES
Research & development $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
Sales & marketing $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
General & administrative $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
-------- -------- -------- -------- --------
TOTAL OPERATING EXPENSES $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
OPERATING INCOME (LOSS) $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
Operating Margin XX.X% XX.X%
OTHER INCOME (EXPENSE)
Interest income $XX,XXX $XX,XXX $X,XXX X.X%
Interest expense ($XX,XXX) ($XX,XXX) $X,XXX X.X%
Other, net $XX,XXX $XX,XXX $X,XXX X.X%
-------- -------- --------
TOTAL OTHER INCOME (EXPENSE) $XX,XXX $XX,XXX $X,XXX X.X%
INCOME BEFORE TAXES $XX,XXX $XX,XXX $X,XXX X.X%
Income tax expense $XX,XXX $XX,XXX $X,XXX X.X%
-------- -------- --------
NET INCOME (LOSS) $XX,XXX $XX,XXX $X,XXX X.X% $XX,XXX $X,XXX
Net Margin XX.X% XX.X%
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.
- 3d ago First seen · 139 lines · 12 tokens per session scan A 72ad6f648be6
income-statement is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,499 once invoked, about $0.0001 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-31.
Other commands, from other repositories
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…