trading-ops: Command for Claude Code

.claude/commands/scan-fundamentals.md

scan-fundamentals is a command for Claude Code from l3lackcurtains/trading-ops. It costs 23 tokens per session (577 once invoked), scanned A, original, MIT.

A command for updating the fundamentals section of a stock analysis scorecard for a given ticker. The scorecard evaluates six areas, including quality, growth, valuation, debt, capital allocation, and investor ownership.

In plain words
What is it for?
Use it after earnings or guidance changes to update the six-pillar assessment, check rejection flags, and revise the fundamentals section of the stock report.
Why use it?
It refreshes business and financial information when fundamentals change without repeating the technical-analysis portion of a full stock scan.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is l3lackcurtains/trading-ops's own configuration. It tells Claude Code how to work on trading-ops itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything trading-ops configures →

Reuse

Borrowing it

Nothing to install: this file belongs to l3lackcurtains/trading-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/l3lackcurtains/trading-ops/main/.claude/commands/scan-fundamentals.md
Clone the repo
git clone --depth 1 https://github.com/l3lackcurtains/trading-ops

Made for: Claude Code.

Wrote 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.

agentmods badge for scan-fundamentals

README.md
[![agentmods](https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/scan-fundamentals/github.svg)](https://agentmods.dev/commands/l3lackcurtains/trading-ops/scan-fundamentals)
Your own site
<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/scan-fundamentals"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/scan-fundamentals/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.

agentmods 80×15 button for scan-fundamentals

Your own site · 80×15
<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/scan-fundamentals"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/scan-fundamentals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 577 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00577
Opus 5 $0.00012 $0.00289
Sonnet 5 $0.00005 $0.00115
Haiku 4.5 $0.00002 $0.00058

Measured 11d ago against content hash 7f05dde884d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

scan-fundamentals 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.

.claude/commands/scan-fundamentals.md · 39 lines

What it actually says

Run a fundamentals-only scan for: $ARGUMENTS

Partial scan — updates only the 6-pillar scorecard section. Use when fundamentals changed (earnings print, guidance update) but the technical setup is unchanged. For a full refresh, use /rescan $ARGUMENTS.

Protocol in guide/scan/ — see scorecard.md for the 6-pillar definitions and structure.md for the section format.

Steps

  1. Verify scanned/stocks/$ARGUMENTS/current.md exists. If not, tell the user to run /scan $ARGUMENTS first.

  2. Read-before-scan per protocol.md — capture prior 6-pillar score + auto-reject flags.

  3. Pull fundamentals data per data.md:

    • Finviz quote page (one WebFetch — covers most pillars)
    • Stockanalysis for FCF / Net Debt / EBITDA detail
    • 13F holders chain (WhaleWisdom → HedgeFollow → Fintel) for Pillar 6
    • Dataroma for superinvestor coverage
    • Insider Form 4 (OpenInsider → Finviz insider page)
  4. Re-run 6-pillar per scorecard.md:

    • Quality (ROIC) / Growth (rev/EPS) / Valuation (P/S, EV/EBIT, FCF yield) / Balance Sheet (Net Debt/EBITDA) / Capital Allocation / Smart Money
    • Score each PASS / FAIL / NEUTRAL with explicit numbers
    • Aggregate /6; check auto-reject flags
  5. Edit only the 6-Pillar Scorecard section of scanned/stocks/$ARGUMENTS/current.md. Leave Technical Read / Trade plan / Coverage tier untouched unless the score change forces a tier transition (Pos S → B requires the auto-reject flags to clear, etc.).

  6. If the Pos tier changes because the score change is material:

    • Update the **Coverage tier:** header line
    • Append a row to scanned/INDEX.md § Coverage changes — last 30 days
    • Per tiers.md § Tier-change protocol
  7. No archive rotation, no rescan rotation — this is an in-place update. The full audit trail comes from /rescan only.

  8. Update INDEX.md master coverage table row's Score column if it changed.

Changes

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.

  1. 11d ago First seen · 39 lines · 23 tokens per session scan A 7f05dde884d3

Subscribe to this mod's changes

scan-fundamentals is a command published in the GitHub repository l3lackcurtains/trading-ops (56 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 577 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.