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 feniix/pi-extensions --skill financial-report-searchgit clone --depth 1 https://github.com/feniix/pi-extensionsWrote 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/feniix/pi-extensions/financial-report-search)<a href="https://agentmods.dev/skills/feniix/pi-extensions/financial-report-search"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/financial-report-search/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/feniix/pi-extensions/financial-report-search"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/financial-report-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00549 |
| Opus 5 | $0.00012 | $0.00275 |
| Sonnet 5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
financial-report-search 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 11d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Report Search (Exa)
Use this skill for SEC filings, annual reports, earnings materials, investor presentations, risk factors, financial metrics, and company-by-company filing comparisons.
Tool Selection
| Intent | Primary Tool | Notes |
|---|---|---|
| Discover filings, annual reports, or investor materials | web_search_advanced_exa with category: "financial report" |
Use when available; date and domain filters are useful here. |
| Broad filing discovery when advanced search is unavailable | web_search_exa |
Add company name, filing type, fiscal year, and source domain terms. |
| Compare filings across firms or periods | web_research_exa |
Use when enabled; require evidence-backed statements. |
| Explain one metric, line item, or disclosure | web_answer_exa |
Good for narrow cited explanations. |
| Read full filing or report text | web_fetch_exa |
Fetch 1-3 selected URLs only. |
If web_search_advanced_exa is unavailable, fall back to web_search_exa with explicit terms like 10-K, 10-Q, annual report, investor relations, site:sec.gov, or the company ticker.
Recommended Settings
- Filing discovery
{ "query": "NVIDIA 10-K 2025 risk factors", "category": "financial report", "startPublishedDate": "2025-01-01", "numResults": 10 }
- SEC-focused discovery
{ "query": "NVIDIA latest 10-K", "category": "financial report", "includeDomains": ["sec.gov", "sec.report"], "numResults": 10 }
- Comparative synthesis
{ "query": "Compare risk factors and revenue trend disclosures in the latest annual reports for NVIDIA, AMD, and Intel.", "systemPrompt": "Return only evidence-backed statements. Separate reported numbers from interpretation and cite source URLs for every numeric claim.", "outputSchema": { "type": "object", "properties": { "summary": { "type": "string" }, "risks": { "type": "array", "items": { "type": "string" } } } } }
Output Guidance
- Separate reported numbers from interpretations.
- Include source links for every numeric claim.
- Call out filing type, period, and publication date.
- Flag stale filings, amended filings, and source ambiguity.
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.
- 11d ago First seen · 38 lines · 23 tokens per session scan A 80e9f78fbf12
financial-report-search is a skill published in the GitHub repository feniix/pi-extensions (23 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 549 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-30.
Other skills, from other repositories
qamap-pr-qa
Local zero-LLM PR QA workflow. Use when an agent is preparing, updating, finalizing, or reviewing a pull request, asks what the PR should test, or needs commit-backed change intent, affected behavior, QA scenarios, evidence, validation commands, optional automation drafts, and manifest repair guidance.
ts-debug
TypeScript/Node debugging expert. Use when the user needs to debug, profile, or trace TypeScript or Node.js code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function", "why won't the process exit".
typescript-conventions
Use when writing, reviewing, or refactoring TypeScript or JavaScript code — naming conventions, type annotations, private fields, null vs. undefined, async/await pitfalls, and module structure.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
setup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.