Borrowing it
Nothing to install: this file belongs to heurist-network/heurist-finance. 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/heurist-network/heurist-finance/main/.claude/skills/trade-postmortem/SKILL.mdgit clone --depth 1 https://github.com/heurist-network/heurist-financeWrote 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/heurist-network/heurist-finance/trade-postmortem)<a href="https://agentmods.dev/skills/heurist-network/heurist-finance/trade-postmortem"><img src="https://agentmods.dev/badge/skills/heurist-network/heurist-finance/trade-postmortem/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/heurist-network/heurist-finance/trade-postmortem"><img src="https://agentmods.dev/badge/skills/heurist-network/heurist-finance/trade-postmortem.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.00093 | $0.01437 |
| Opus 5.5 | $0.00037 | $0.00575 |
| Sonnet 5.5 | $0.00019 | $0.00287 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
trade-postmortem 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 13d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trade Postmortem
Shared plumbing and output contract: ../_shared/analyst-core.md. The feedback loop is where a trader either compounds skill or compounds superstition — and P&L alone teaches the wrong lessons, because markets pay bad process often enough to reinforce it. This skill closes the loop that trading-plan opens: the plan documents in trading/plans/ are the exam answer key; the postmortem grades against them.
The 2×2 (grade every trade on both axes)
| Followed the plan | Broke the plan | |
|---|---|---|
| Made money | Skill (or well-bought variance). Reinforce. | The dangerous quadrant — a paid mistake trains repetition; flag it louder than any loss |
| Lost money | Tuition — the plan bought variance and variance arrived. Check whether the plan itself was sound; often change nothing | Compound error — but the fix is one process rule, not a new system |
The paid-mistake quadrant is the reason this skill exists: profitable rule-breaking is the most reinforcing event in trading and the most corrosive. Say it plainly when found.
Hindsight-proof attribution (the hard part done honestly)
Judging a decision by information available after it is the universal postmortem failure. Reconstruct the as-of-then view before grading:
- What was knowable at entry: the plan document's thesis and scenario table; the as-of-then narrative, reconstructed from dated articles via WebSearch; macro as then reported — use
fred macro_vintage_history(this is exactly what vintage data exists for: the payroll number the user traded on, not its later revision); prices/IV at the time fromprices. - If the reported fills conflict with the verified tape (a price that never traded that day, a date with no such move): don't silently accept or correct. Grade the reported structure on process, flag the tape conflict explicitly, and cross-check whether the narrative's shape (direction, rough timing) survives on the real bars — if it doesn't, the postmortem's first finding is the record-keeping.
- Then the four-way attribution, each scored right/wrong given that reconstruction: Thesis (did the predicted mechanism operate?), Timing (right thesis, wrong clock is the most common split verdict — note it feeds sizing, not thesis, next time), Sizing (did size force a behavioral exit before the thesis resolved? cross-ref
position-sizing's 11pm test), Exit (against the plan's invalidation list: did they exit on signal, on noise, or on pulse? — the field card's noise/signal split, applied retroactively). - Counterfactual honestly bounded: "would've made X if held" uses the plan's exit rule as the counterfactual, never the peak price — the peak was only visible in hindsight, and grading against it manufactures regret, which drives the next oversize.
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.
- 13d ago First seen · 45 lines · 93 tokens per session scan A fe045481830d
trade-postmortem is a skill published in the GitHub repository heurist-network/heurist-finance (11 stars, last pushed 14d ago), licensed MIT. It adds 93 tokens to every session and 1,437 once invoked, about $0.0004 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-10-24.
trade-postmortem compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| trade-postmortemheurist-network/heurist-finance | Skill | 11 | 14d ago | MIT | A | 93 | Claude Code |
| sector-rotationHKUDS/Vibe-Trading | Skill | 38k | yesterday | MIT | A | 39 | Claude Code, Codex |
| twitter-readerhimself65/finance-skills | Skill | 3.5k | 2d ago | MIT | A | 110 | Claude Code |
| strategy-pivot-designertradermonty/claude-trading-skills | Skill | 3.7k | 2d ago | MIT | A | 28 | Claude Code, Codex |
| energy-procurementhashgraph-online/awesome-codex-plugins | Skill | 1.5k | yesterday | Apache-2.0 | A | 93 | Claude Code, Codex |
| airdrop-hunting-guidenirholas/three.ws | Skill | 269 | yesterday | Apache-2.0 | A | 54 | Claude Code, Codex |
| multi-expert-analyzerdigoal/blog | Skill | 8.6k | 2d ago | GPL-2.0 | A | 292 | Codex |