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 skills/zircote-plugins/sigint/financial-analysisnpx skills add zircote-plugins/sigint --skill financial-analysisgit clone --depth 1 https://github.com/zircote-plugins/sigintWrote 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/zircote-plugins/sigint/financial-analysis)<a href="https://agentmods.dev/skills/zircote-plugins/sigint/financial-analysis"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/financial-analysis.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.00065 | $0.01944 |
| Opus 5 | $0.00032 | $0.00972 |
| Sonnet 5 | $0.00013 | $0.00389 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
financial-analysis 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 4d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Analysis
Overview
Financial analysis evaluates economic viability and business model health through metrics, projections, and benchmarking. This skill covers key financial frameworks for market and business analysis.
Required Frameworks
| Framework | Output Section | Required | Condition |
|---|---|---|---|
| Unit Economics | Unit Economics | yes | — |
| Revenue Model Classification | Revenue Model | yes | — |
| Pricing Strategy | Pricing Analysis | yes | — |
| Cost Structure | Cost Structure | yes | — |
| Rule of 40 | Profitability Assessment | yes | — |
Trend Indicators: Load and apply the trend indicator definitions from protocols/TREND-INDICATORS.md.
Core Metrics
Unit Economics
Customer Acquisition Cost (CAC)
- Total sales & marketing spend ÷ new customers acquired
- Benchmark: Varies by industry ($50-$500+ for SaaS)
Lifetime Value (LTV)
- Average revenue per customer × gross margin × customer lifetime
- Simplified: ARPU ÷ churn rate × gross margin
LTV:CAC Ratio
- Target: 3:1 or higher
- <1:1 = unsustainable
-
5:1 = may be under-investing
Payback Period
- CAC ÷ (ARPU × gross margin)
- Target: <12 months for SaaS
Revenue Metrics
Monthly Recurring Revenue (MRR)
- Sum of all recurring subscription revenue
Annual Recurring Revenue (ARR)
- MRR × 12
Average Revenue Per User (ARPU)
- Total revenue ÷ number of customers
Net Revenue Retention (NRR)
- (Starting MRR + expansion - contraction - churn) ÷ Starting MRR
- Target: >100% (expansion exceeds churn)
Growth Metrics
Month-over-Month Growth
- (Current MRR - Previous MRR) ÷ Previous MRR
Year-over-Year Growth
- (Current ARR - Previous Year ARR) ÷ Previous Year ARR
Compound Annual Growth Rate (CAGR)
- ((End Value ÷ Start Value)^(1/years)) - 1
Revenue Models
Subscription (SaaS)
- Recurring monthly/annual payments
- Metrics: MRR, ARR, churn, NRR
- Trend: INC (dominant model)
Usage-Based
- Pay per consumption
- Metrics: Usage growth, ARPU, expansion rate
- Trend: INC (growing adoption)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 271 lines · 65 tokens per session scan A 6beb8f1b61fc
financial-analysis is a skill published in the GitHub repository zircote-plugins/sigint (20 stars, last pushed 18d ago), licensed MIT. It adds 65 tokens to every session and 1,944 once invoked, about $0.0003 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 skills, from other repositories
gr-competitor
竞品深度扫描。批量抓取对手落地页（title/h1/intro/pricing）、定价页、博客 top 10、 变更历史（Wayback）。底层调 actionbook（并发 30 tab + 省 90% token）。 当用户说"分析对手"、"看看竞品在做啥"、"找对标"、"扫一下 top 10"时调用。.
radar-merge-briefing
Merges all competitor dossiers and the change set into one briefing. Writes three local artifacts: the briefing markdown, a combined raw dossier JSON, and a dashboard data JSON. Use after radar-diff-changes and before radar-publish-notion and radar-render-dashboard. Every claim in the briefing carries a source URL.
radar-publish-council
Publishes the Strategic War Room addendum from /radar-council to all three surfaces. Appends the addendum to the local briefing markdown, fills the warroom section of the dashboard data and re-renders the dashboard, and appends the addendum to the Notion briefing page while checking its War Room box. Use after the…
radar-onboard
Run this FIRST, before any other radar skill. Sets up Competitive Intelligence Radar by ASKING whether BrightData and Notion are connected, live-testing one real call to each, detecting which MCP prefix is actually live, and writing radar.config.json with the user's business context. Use when the user runs…
radar-provision-notion
Creates the two Notion databases (Competitors and Briefings) the radar publishes to, but ONLY after SHOWING the proposed schema and getting the user's explicit approval. Use during /radar-setup after onboarding, or when radar-publish-notion reports the databases are missing. Idempotent: if the databases already exist…
radar-publish-notion
Publishes the run to Notion. Upserts one row per competitor in the Competitors database (matched by domain, with a Change field for week-over-week tracking) and creates a Briefings page holding the full briefing. Use after radar-merge-briefing. Requires the databases to exist (radar-provision-notion). Writing rows to…