alpacalyzer-algo-trader: Skill for Claude Code

.agents/skills/validate-e2e/SKILL.md

validate-e2e is a skill for Claude Code, Codex from kimrejstrom/alpacalyzer-algo-trader. It costs 27 tokens per session (423 once invoked), scanned A, original, MIT.

A procedure for checking a trading application from start to finish in dry-run mode, which tests the flow without placing real trades. It reads the result as structured JSON data.

In plain words
What is it for?
Use it after modifying scanners, agents, strategies, or execution code to check run status, found opportunities, generated strategies, queued signals, and errors.
Why use it?
It shows whether scanning, strategy creation, signal queuing, and error handling still work together after a change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is kimrejstrom/alpacalyzer-algo-trader's own configuration. It tells Claude Code and Codex how to work on alpacalyzer-algo-trader 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 alpacalyzer-algo-trader configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kimrejstrom/alpacalyzer-algo-trader. 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/kimrejstrom/alpacalyzer-algo-trader/main/.agents/skills/validate-e2e/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kimrejstrom/alpacalyzer-algo-trader

Made for: Claude Code, Codex.

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 validate-e2e

README.md
[![agentmods](https://agentmods.dev/badge/skills/kimrejstrom/alpacalyzer-algo-trader/validate-e2e/github.svg)](https://agentmods.dev/skills/kimrejstrom/alpacalyzer-algo-trader/validate-e2e)
Your own site
<a href="https://agentmods.dev/skills/kimrejstrom/alpacalyzer-algo-trader/validate-e2e"><img src="https://agentmods.dev/badge/skills/kimrejstrom/alpacalyzer-algo-trader/validate-e2e/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 validate-e2e

Your own site · 80×15
<a href="https://agentmods.dev/skills/kimrejstrom/alpacalyzer-algo-trader/validate-e2e"><img src="https://agentmods.dev/badge/skills/kimrejstrom/alpacalyzer-algo-trader/validate-e2e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 423 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.00027 $0.00423
Opus 5.5 $0.00011 $0.00169
Sonnet 5.5 $0.00005 $0.00085
Haiku 4.5 $0.00003 $0.00042

Measured 2mo ago against content hash c1ffb12384c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-e2e 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 2mo 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.

.agents/skills/validate-e2e/SKILL.md · 55 lines

What it actually says

Validate End-to-End Skill

When to Use

After making changes to the trading pipeline (scanners, agents, strategies, execution), validate that the full flow still works by running a dry-run cycle.

How to Validate

uv run alpacalyzer --analyze --dry-run --json 2>/dev/null

This runs one analysis cycle and outputs structured JSON to stdout:

{
  "status": "ok",
  "mode": "dry_run",
  "tickers_scanned": ["AAPL", "TSLA", "NVDA"],
  "opportunities": 3,
  "strategies_generated": 2,
  "signals_queued": 2,
  "errors": []
}

What to Check

  1. status should be "ok" — any other value means something broke
  2. errors should be empty — non-empty means a component failed
  3. opportunities > 0 — if zero, scanners may be broken
  4. strategies_generated > 0 — if zero, agents may be broken

With Specific Tickers

uv run alpacalyzer --analyze --dry-run --json --tickers AAPL,MSFT 2>/dev/null

Interpreting Failures

  • "status": "error" with "errors": ["scanner timeout"] → Scanner issue
  • opportunities: 0 → Check scanner adapters and API keys
  • strategies_generated: 0 with opportunities > 0 → Agent/LLM issue
  • Any Python traceback on stderr → Code error (the 2>/dev/null hides stderr; remove it to debug)

Integration with CI

This is not wired into CI (it requires API keys). Use it locally after making pipeline changes.

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. 2mo ago First seen · 55 lines · 27 tokens per session scan A c1ffb12384c4

Subscribe to this mod's changes

validate-e2e is a skill published in the GitHub repository kimrejstrom/alpacalyzer-algo-trader (2 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 423 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-31.

Related

validate-e2e compared with skills from other repositories

validate-e2e next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
validate-e2ekimrejstrom/alpacalyzer-algo-traderSkill25mo agoMITA27Claude Code, Codex
verify-omnigentomnigent-ai/omnigentSkill11kyesterdayApache-2.0A100Claude Code, Codex
test-masterJeffallan/claude-skillsSkill12k7d agoMITA104Claude Code
eval-dataset-designbojieli/ai-agent-bookSkill57k29d agoApache-2.0A138Claude Code, Codex
dogfoodcallstack/agent-deviceSkill5.3kyesterdayMITA55Claude Code
cua-driverdavidondrej/skillsSkill4.3k3d agoMITA68Claude Code, Codex
test-warp-uiwarpdotdev/warpSkill66kyesterdayAGPL-3.0A55Claude Code