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.
curl -O https://raw.githubusercontent.com/l3lackcurtains/trading-ops/main/.claude/commands/ingest.mdgit clone --depth 1 https://github.com/l3lackcurtains/trading-opsWrote 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/l3lackcurtains/trading-ops/ingest)<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/ingest"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/ingest/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/l3lackcurtains/trading-ops/ingest"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/ingest.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.00022 | $0.02611 |
| Opus 5.5 | $0.00009 | $0.01044 |
| Sonnet 5.5 | $0.00004 | $0.00522 |
| Haiku 4.5 | $0.00002 | $0.00261 |
Grade A, and why
ingest 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 1mo 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ingest — knowledge intake + protocol recalibration
/ingest <source> is the single authorized writer inside docs/. Every other command, freeform action, scan, and the self-improvement loop treats docs/ as read-only. This command is the carve-out.
What it does
- Parse the source — file path / URL / inline text or idea
- Read or fetch the content
- Classify the knowledge — new framework doc · extension of existing doc · pure protocol/data-source change (which doesn't belong in docs/)
- Propose a write plan — what gets created/edited in
docs/, what gets recalibrated inguide/, what cross-references update - Apply only after user consent
- Run link validation
- Append an entry to
docs/INGEST_LOG.md
Argument forms
| Form | Example | Behavior |
|---|---|---|
| File path | /ingest input/spotgamma-2026.pdf |
Read local file (PDF, MD, TXT). For PDFs, use the Read tool's pages param for files > 10 pages. |
| URL | /ingest https://example.com/paper |
WebFetch the URL. Use chrome-devtools for dynamic pages. |
| Inline text or idea | /ingest "Add dealer-positioning section to macro.md — when SPX gamma flips negative, dealers buy rallies and sell dips. Source: Nomura/McElligott." |
The argument itself is the knowledge to ingest |
| No args | /ingest |
Show help + last 5 entries from docs/INGEST_LOG.md |
Steps
Step 1 — Parse + classify the source
Determine:
- Source type — file / URL / inline
- Content domain — macro · long-term-investing · technical (VWAP/VP) · options/dealer flow · news-trading · new asset class · new tool/methodology
- Scope — new doc · append to existing doc · cross-cutting (touches multiple docs)
- Where it lands — does this create knowledge (docs/), or only change how we apply it (guide/)? If the latter, this is a self-improvement-loop change, not an
/ingest. Don't write to docs/ if the change is purely procedural.
If the classification is ambiguous, ask the user before continuing.
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.
- 1mo ago First seen · 204 lines · 22 tokens per session scan A 76bc20bc71e3
ingest is a command published in the GitHub repository l3lackcurtains/trading-ops (57 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 2,611 once invoked, about $0.0001 per session on Opus 5.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
execute-entry
Execute a new MEICAgent iron condor entry. Only invoke when the entry decision (Step 6) is yes.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.