journal-pattern-analyzer

journal-pattern-analyzer is a skill for Claude Code, Codex from marian2js/trading-skills. It costs 38 tokens per session (1,209 once invoked), scanned A, original, MIT.

A method for reviewing a group of trades or trading notes to find repeated strengths, mistakes, and conditions that affect results. It focuses on how decisions were made, not just whether the trades made or lost money.

In plain words
What is it for?
It is for finding recurring issues in entries, exits, position size, timing, or handling of events, then turning those findings into a small number of process changes.
Why use it?
It helps reveal process problems that a single trade review can miss, without treating a small sample as proof of a lasting advantage.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for finding recurring issues in entries, exits, position size, timing, or handling of events, then turning those findings into a small number of process changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marian2js/trading-skills/journal-pattern-analyzer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add marian2js/trading-skills --skill journal-pattern-analyzer
Clone the repo
git clone --depth 1 https://github.com/marian2js/trading-skills

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 journal-pattern-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/marian2js/trading-skills/journal-pattern-analyzer/github.svg)](https://agentmods.dev/skills/marian2js/trading-skills/journal-pattern-analyzer)
Your own site
<a href="https://agentmods.dev/skills/marian2js/trading-skills/journal-pattern-analyzer"><img src="https://agentmods.dev/badge/skills/marian2js/trading-skills/journal-pattern-analyzer/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 journal-pattern-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/marian2js/trading-skills/journal-pattern-analyzer"><img src="https://agentmods.dev/badge/skills/marian2js/trading-skills/journal-pattern-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,209 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.00038 $0.01209
Opus 5 $0.00019 $0.00605
Sonnet 5 $0.00008 $0.00242
Haiku 4.5 $0.00004 $0.00121

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

Security

Grade A, and why

journal-pattern-analyzer 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 10d 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.

skills/review-learning/journal-pattern-analyzer/SKILL.md · 119 lines

How it starts

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

Journal Pattern Analyzer

Use this skill when the user has a set of trades, journal notes, or review entries and wants to know what patterns are repeating across them.

This skill will not:

  • grade the user only by total PnL
  • pretend a small sample proves a durable edge
  • replace single-trade post-mortems when the problem is still one specific position

Role

Act like a process analyst reviewing a journal, not a cheerleader reviewing outcomes. Your job is to identify repeatable strengths, repeatable mistakes, and where the user's process breaks down under specific conditions.

When to use it

Use it when the user wants to:

  • review a batch of trades instead of one trade
  • identify recurring mistakes in entries, exits, sizing, timing, or catalyst handling
  • see whether performance changes by setup, regime, instrument, or time horizon
  • convert raw journal notes into one or two high-value process changes

Inputs and context

Ask for:

  • a trade log, journal entries, or a summarized set of closed trades
  • the sample window: last 10 trades, last month, last quarter, earnings season, and so on
  • what fields exist: setup type, thesis, entry, stop, target, size, result, notes, adherence, catalyst context
  • whether the user wants to focus on behavioral patterns, setup quality, sizing quality, or environment fit

Helpful but optional:

  • regime notes
  • sector or instrument tags
  • whether results are in dollars, percentages, or R multiples
  • any pattern the user already suspects

Use the user's materials first.

If the sample is very small, say so clearly and keep the conclusions provisional.

For agents that support code execution, use references/calculation-helpers.md for the shared helper functions that cover trade-statistic summaries, expectancy, and win/loss distribution checks when the user provides structured results.

Analysis process

  1. Reconstruct the journal sample and what the user is trying to learn.
  2. Group trades by setup, environment, mistake type, instrument, or catalyst context when the data supports it.
  3. Separate outcome patterns from process patterns.
  4. Identify recurring strengths and recurring mistakes.
  5. Check whether the user's mistakes cluster around specific conditions such as open entries, event holds, oversizing, or late exits.
  6. Distill the findings into one or two process changes that are specific enough to test.
  7. End with what the user should keep doing, stop doing, and monitor next.

Read the full file on GitHub · 119 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 119 lines · 38 tokens per session scan A 9b169543ec9c

Subscribe to this mod's changes

journal-pattern-analyzer is a skill published in the GitHub repository marian2js/trading-skills (11 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,209 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

tushare

A Python interface for Tushare, a financial data service that provides market and company information for stocks, funds, futures, and digital assets. It returns queried data as pandas tables.

HKUDS/Vibe-Trading · 79 tokens

social-media-intelligence

Social media intelligence: financial signal extraction from Twitter/X, Telegram, Discord, and Reddit for sentiment-driven trading strategies.

HKUDS/Vibe-Trading · 28 tokens

credit-analysis

A guide to analysing bonds and other fixed-income investments, including issuer credit quality, interest payments, default risk, credit spreads, and convertible bonds. It also covers Chinese fixed-income markets and local-government financing bonds.

HKUDS/Vibe-Trading · 36 tokens

geopolitical-risk

Geopolitical risk analysis: quantify crisis signals, identify precursors, and build event-driven strategies for war, sanctions, and supply disruption scenarios.

HKUDS/Vibe-Trading · 34 tokens

vibe-trading

Professional finance research toolkit — backtesting (10 engines + benchmark comparison panel), factor analysis, Alpha Zoo (462 pre-built alphas across qlib158/alpha101/gtja191/academic/fundamental), options pricing, 90 finance skills, 30 multi-agent swarm teams, Trade Journal analyzer, and Shadow Account (extract →…

HKUDS/Vibe-Trading · 173 tokens

etf-analysis

A framework for comparing exchange-traded funds (ETFs), which are funds bought and sold on a stock exchange and usually track an index, industry, asset, or strategy. It covers fees, how closely an ETF follows its target, trading activity, and portfolio use.

HKUDS/Vibe-Trading · 39 tokens