agentleFS
Sign inStart free
JakeschincariolJakeschincariol/trader-skill/trader-budget/SKILL.md

trader-budget

Skill14 starsChanged 29 days agoMITView on GitHub

Budget Manager. Sizes every position to your budget before anything is bought: keeps a cash buffer, caps any one stock (the excess is shared out to the others), drops slices under your minimum order, rounds so every dollar is used, supports fractional or whole shares, and writes the proposed buy orders to trader/orders.json in the exact shape of Alpaca's place_stock_order (notional as a string). Nothing is placed. Use when the user says "I have $5,000", "size my trades", "how much of each should I buy", "manage my budget", "split my money", "keep 10% in cash", "no stock over 25%", "set my rules", or after /trader-copycat writes targets.

5 other projects use a version of this, 4 of them edited; 3 new projects in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 3 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 2 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use trader-entry, trader-exit and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JakeschincariolSkill

    trader-entry

    Entry Timer. Watches a setup bar by bar and tells you the moment to get in. Reads free Yahoo 1-minute or 5-minute bars, builds the opening range (the first 15 minutes by default) and calls the entry on the first completed bar that CLOSES above the range high, or above a level you give it (like a 20-day high from the scanner), with an optional volume check. Says waiting and how far, triggered with the time and the price, expired, or not open yet, and writes trader/entry.json for /trader-exit. Long side only. It never places an order. Use when the user says "tell me when to get in", "watch TSLA", "has it broken out", "did it break the opening range", "entry signal", "time my entry", "check my watchlist", or after /trader-scanner and /trader-news, before /trader-exit.

    Also in 4 projects that use this

  • JakeschincariolSkill

    trader-exit

    Exit Planner. Sets your stop and your target before you enter, so you know when to get out. Reads the entry from trader-entry (or a price you give), puts the stop at the opening-range midpoint by default (or the range low, your price, a percent, or a multiple of the ATR), rounds it down to the cent, and sets the target at 2R (or 1R, or your price). Refuses a stop at or above the entry, a target at or below it, or a stop too tight to survive the spread, and says why. Writes trader/plan.json for the Time Machine, the Budget Manager and Price Alerts. Long side only. Use when the user says "where's my stop", "set my stop and target", "plan the exit", "when do I get out", "stop loss", "what's my R", "risk reward", or right after /trader-entry triggers, before /trader-timemachine.

    Also in 4 projects that use this

  • +2 more from Jakeschincariol

The file

We split this skill into the rules it gives an agent

7 rules. 4 are common, 2 are distinctive, and 1 is very specific to this project.

  • 4

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If trader/config.json does not exist, copy config.example.json into trader/config.json and ask the user for each value in plain words:

    line 42
  2. Common:

    Keep paper true until they have watched it work on a paper account.

    line 51
  3. Distinctive:

    Keep the weights to two decimals or more: weights already rounded to one decimal (30.7 / 23.9 / ...) can move a slice by a dollar.

    line 94
  4. Common:

    Never size money the user has not said is for this.

    line 100
  5. Common:

    Every number comes from the config, the targets or the prices.

    line 101
  6. Distinctive:

    No projections: never say what the positions will be worth or earn.

    line 102
  7. Common:

    No options, margin, short selling or leverage unless the config allows it and the user confirms.

    line 118

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

trader-budget

The Budget Manager turns "copy this portfolio" into "buy exactly this much of each", inside rules the user sets once. It writes proposals only. trader-risk checks them and trader-broker asks the user yes or no for each one.

${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).

python3 "${CLAUDE_SKILL_DIR}/size.py"                       # trader/targets.json + trader/config.json
python3 "${CLAUDE_SKILL_DIR}/size.py" --budget 5000 --write # write trader/orders.json
python3 "${CLAUDE_SKILL_DIR}/size.py" --whole-shares --prices trader/prices.json
python3 "${CLAUDE_SKILL_DIR}/size.py" --weights AAPL=22.04,AXP=17.14,GOOGL=12.62 --json

What it reads and writes

filewhat
trader/config.jsonthe rules (start from config.example.json in this folder)
trader/targets.jsonthe weights to copy, written by trader-copycat (targets.example.json here)
trader/prices.jsononly for whole shares or share counts (trader-alerts writes it)
trader/orders.jsonthe proposed buy orders it writes with --write

Step 1: set the rules once

If trader/config.json does not exist, copy config.example.json into trader/config.json and ask the user for each value in plain words:

  • budget: how much money this is for. Only money they can afford to lose.
  • cash_buffer_pct: how much stays in cash (default 10).
  • max_position_pct: the most any one stock may be, as a percent of the budget (default 25).
  • max_order_usd and min_order_usd: the biggest and smallest single order (2000 and 5).
  • fractional: true if the broker buys fractional shares (Alpaca does); false for whole shares.
  • blocked: tickers they never want to own.
  • Keep paper true until they have watched it work on a paper account.

Step 2: size it

python3 "${CLAUDE_SKILL_DIR}/size.py" --write

The maths, in order: the cash buffer comes off the top; the weights are renormalised to 100 over the stocks that are left; any stock over the cap is pinned at the cap and its excess is shared over the others by weight, again until nobody is over; a slice under the minimum order is dropped and its weight shared out; amounts are rounded to whole dollars and the rounding dollar goes to the biggest stock that is not capped, so nothing is left idle by accident. Money that truly cannot be invested (every stock at its cap, or whole shares that do not divide evenly) is shown as "left idle".

Step 3: show the user

Show the table: ticker, weight, dollars, which stock hit the cap, the cash buffer and what is left idle. Say where the weights came from and how old they are (a 13F is up to 45 days old when it is filed). Then hand over to /trader-risk.

Example: the reel

Berkshire Hathaway's Q2 2026 13F (filed 2026-08-14), top five: Apple 22.04%, American Express 17.14%, Alphabet 12.62%, Coca-Cola 10.86%, Bank of America 9.20%. Renormalised over those five: 30.67 / 23.85 / 17.56 / 15.11 / 12.80. A $5,000 budget, a 10% cash buffer and a 25% cap:

stockdollars
AAPL$1,250capped at 25%
AXP$1,119
GOOGL$823
KO$708
BAC$600
cash buffer$500
left idle$0

The first order it writes is {"symbol": "AAPL", "side": "buy", "notional": "1250", "type": "market", "time_in_force": "day"}. Keep the weights to two decimals or more: weights already rounded to one decimal (30.7 / 23.9 / ...) can move a slice by a dollar.

Rules

  • Proposals only. This skill never calls a broker tool.
  • Never size money the user has not said is for this. Ask for the budget.
  • Every number comes from the config, the targets or the prices. Nothing is guessed.
  • No projections: never say what the positions will be worth or earn.
  • Whole shares need real prices from trader/prices.json; never invent a price.

What it never does

It never places, approves or schedules an order, never raises a limit on its own, and never sizes options, margin or short positions.

Safety

  • Education and tooling, not financial advice. Nothing here predicts prices or promises returns.
  • Paper trading by default ("paper": true). Going live is the user's own decision, in their own config.
  • Nothing in this pack places an order except trader-broker, and only when all three hold: trader-risk passed that exact order today, the user typed an explicit yes for that one order in the chat, and the user clicked Allow once on Claude's own card because the order tool is set to "Needs approval" (Customize > Connectors > tool permissions). Never set an order tool to "Always allow".
  • No options, margin, short selling or leverage unless the config allows it and the user confirms.
  • Broker keys live in environment variables or the Claude Desktop config, never in the chat.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free