What is pead-tracker?

A workflow for tracking post-earnings announcement drift, the tendency for a stock to keep moving in the direction of an earnings surprise after results are published.

Use it to examine portfolio holdings after earnings, identify ongoing drift after beats or misses, and produce per-stock decisions such as buy, sell, trim, or hold.

It keeps portfolio decisions consistent with earlier decisions while checking whether an earnings-related price move is continuing.

How tusharagg1/aifolimizer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tusharagg1/aifolimizer. 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/tusharagg1/aifolimizer/master/.claude/skills/pead-tracker/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tusharagg1/aifolimizer

Made for: Claude Code.

Or install aifolimizer, the plugin that ships this one along with the rest of its 28 skills, 2 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tusharagg1/aifolimizer/pead-tracker/github.svg)](https://agentmods.dev/skills/tusharagg1/aifolimizer/pead-tracker)

Your own site

<a href="https://agentmods.dev/skills/tusharagg1/aifolimizer/pead-tracker"><img src="https://agentmods.dev/badge/skills/tusharagg1/aifolimizer/pead-tracker/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tusharagg1/aifolimizer/pead-tracker"><img src="https://agentmods.dev/badge/skills/tusharagg1/aifolimizer/pead-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,891 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.

Model	Per session	Once invoked
Fable 5.1	$0.00117	$0.01891
Opus 5	$0.00059	$0.00945
Sonnet 5	$0.00023	$0.00378
Haiku 4.5	$0.00012	$0.00189

Measured 8d ago against content hash 3beab1866468, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pead-tracker 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 8d 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/skills/pead-tracker/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PEAD Tracker (Post-Earnings Announcement Drift)

Stage 0 - Decision Memory (load FIRST)

Before analysis, load prior decisions so verdicts stay consistent across sessions:

mcp__aifolimizer__get_cross_ticker_lessons with max_lessons=3 - portfolio-level win/loss patterns
For any name you issue a per-ticker BUY/SELL/TRIM/HOLD on, also load mcp__aifolimizer__get_ticker_decision_history (ticker=…, max_decisions=5) and mcp__aifolimizer__get_ticker_reflection (symbol=…, n=3).

Reconciliation rule: if a prior decision exists and your new read flips it, state explicitly WHY it changed (new data / catalyst / price move). Never silently contradict a logged decision - that drift is exactly what this prevents.

Research basis

Bernard & Thomas (1989): stocks keep moving in direction of earnings surprise after earnings are public. Drift window: ~60 trading days (~85 calendar days) from report date. Expected abnormal return by size: small firms +5.1%, mid +4.3%, large +2.8%.

How to run

Call mcp__aifolimizer__get_profile - account types and capital context
Call mcp__aifolimizer__get_portfolio - full holdings list
Call mcp__aifolimizer__get_earnings_results with all held symbols, quarters=2 - get report dates, surprise %, outcome for last 2 quarters
Call mcp__aifolimizer__get_fundamentals for all symbols - market cap (determines expected drift magnitude), analyst target
Call mcp__aifolimizer__get_technicals for symbols with active drift - pct_from_52w_high, RSI, trend to assess whether drift is still running or exhausted

Call steps 3-5 in parallel after step 2 resolves.

Drift window logic

Use ONE clock - calendar days - throughout, to avoid mixing trading-day and calendar-day units. The ~60-trading-day Bernard-Thomas window ≈ 85 calendar days; we measure everything against that 85-day calendar window.

For each holding with a recorded earnings report:

Compute calendar days since report date (use today's date)
Active window: 0-85 calendar days since report
Late window: 55-85 calendar days (drift fading - last chance to ride or exit)
Expired: > 85 calendar days (no PEAD edge remaining)

Read the full file on GitHub · 106 lines

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.

8d ago First seen · 106 lines · 117 tokens per session scan A 3beab1866468

Subscribe to this mod's changes

pead-tracker is a skill published in the GitHub repository tusharagg1/aifolimizer (2 stars, last pushed 7d ago), licensed MIT. It adds 117 tokens to every session and 1,891 once invoked, about $0.0006 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-31.

Analytics and metrics Claude Code Finance and fintech ai-agents backtesting claude-desktop fastapi fastmcp

quantoracle

63 deterministic quantitative finance calculators + 10 composite workflows via MCP. Options pricing, Greeks, exotic derivatives, risk metrics, portfolio optimization, Monte Carlo, statistics, crypto/DeFi, FX/macro, TVM, strategy backtesting, rebalance planning, options strategy selection, hedging. 1,000 free…

QuantOracledev/quantoracle · 92 tokens

gitee-expert

You have access to Gitee (gitee.com), China's largest GitHub-style platform. This skill teaches the effective workflows for discovery, intel, translation and webhook monitoring.

sandraschi/gitee-mcp · 0 tokens

transcribe-filing

Transcribe an insurance rate filing or internal rating manual into an OpenRater workbook, then validate, build, verify, and rate it through the OpenRater MCP tools. Use when the user shares a filing/manual (PDF or pages) and wants it executable — "build this filing", "digitize this rating manual", "make this rateable"…

vadim-filimonov/openrater · 102 tokens

aifolimizer: Skill for Claude Code