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.
git clone --depth 1 https://github.com/yuping322/financial-services-plugins-newWrote 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/yuping322/financial-services-plugins-new/earnings)<a href="https://agentmods.dev/commands/yuping322/financial-services-plugins-new/earnings"><img src="https://agentmods.dev/badge/commands/yuping322/financial-services-plugins-new/earnings/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/commands/yuping322/financial-services-plugins-new/earnings"><img src="https://agentmods.dev/badge/commands/yuping322/financial-services-plugins-new/earnings.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.00009 | $0.01145 |
| Opus 5 | $0.00005 | $0.00573 |
| Sonnet 5 | $0.00002 | $0.00229 |
| Haiku 4.5 | $0.00001 | $0.00114 |
Grade A, and why
earnings 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 9d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Earnings Analysis Command
Create a professional equity research earnings update report analyzing quarterly results.
Workflow
Step 1: Gather Information
Parse the input for:
- Company name or ticker
- Quarter (e.g., Q3 2024, Q2 FY25)
If not provided, ask:
- "What company's earnings would you like to analyze?"
- "Which quarter? (e.g., Q3 2024)"
Step 2: Verify Timeliness
CRITICAL: Before proceeding, verify you have the latest data:
- Search for "[Company] latest earnings results [current year]"
- Verify the earnings release is within the last 3 months
- Confirm transcript date matches release date
If data is stale, inform the user and search for the latest.
Step 3: Load Earnings Analysis Skill
Use skill: "earnings-analysis" to create the report:
-
Data Collection (search for latest):
- Earnings release (press release)
- 10-Q filing from SEC EDGAR
- Earnings call transcript
- Investor presentation/supplemental materials
- Consensus estimates (Bloomberg/FactSet)
-
Beat/Miss Analysis:
- Revenue vs consensus: Beat/Miss by $X or X%
- EPS vs consensus: Beat/Miss by $X or X%
- Key segment performance vs expectations
- Explain WHY results differed
-
Key Metrics Analysis:
- Revenue breakdown by segment/geography
- Margin trends (gross, operating, net)
- Guidance: raised/maintained/lowered
- Updated forward estimates
-
Generate Charts (8-12):
- Quarterly revenue progression
- Quarterly EPS progression
- Margin trends
- Revenue by segment
- Beat/miss summary
- Estimate revisions
- Valuation charts
-
Create Report (8-12 pages):
- Page 1: Summary with rating and price target
- Pages 2-3: Detailed results analysis
- Pages 4-5: Key metrics & guidance
- Pages 6-7: Updated investment thesis
- Pages 8-10: Valuation & estimates
- Sources section with clickable hyperlinks
Step 4: Deliver Output
Provide:
- DOCX report - 8-12 page earnings update
- Summary highlighting:
- Beat/miss on key metrics
- Guidance changes
- Thesis impact (positive/negative/neutral)
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.
- 9d ago First seen · 141 lines · 9 tokens per session scan A 7dea0e12d0c8
earnings is a command published in the GitHub repository yuping322/financial-services-plugins-new (17 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 1,145 once invoked, about $0.0000 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.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
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…
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.