DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trace top broker buying and selling in an IDX stock with Idx

See which brokers lead buying and selling in one ticker and whether a bandar phase is showing.

Who it is forA trader who reads broker flow on IDX and wants a quick view of the top buyers and sellers for one ticker.

The problemBroker-level buying and selling is not shown on the standard quote pages, so the top movers are hard to see.

The outcomeThe top 10 buyers and sellers of a ticker by lots, with broker class, value and average price, plus an accumulation or distribution read.

What you need first

  • Rust 1.88 or newer for cargo install, or Node.js and npm for the npm route
  • An internet connection for the first run (offline mode serves cached data only)
  • A terminal on Linux, macOS or Windows

Steps

  1. Install Idx with npm install -g github:fzn0x/idx or cargo install ihsg-cli.
  2. Run idx broker BBCA to see the top 10 buyers and sellers for the latest session with trades. (inferred, check the README)
  3. Run idx bandar detect BBCA --period 1w to check whether the top brokers are accumulating or distributing over a week. (inferred, check the README)
  4. Run idx -o csv broker BBCA if you want one row per broker for a spreadsheet, using the csv output option the README describes. (inferred, check the README)

Prompt for your agent

Use the idx tool from the fzn0x/idx repo to run `idx broker <ticker>` and `idx bandar detect <ticker> --period 1w` for <ticker such as BBCA>. Return the top buyers, top sellers and the accumulation or distribution read. Verify that the output reports the session date and states whether the phase is accumulation or distribution.

Caveat. Bandarmology is a reading of broker flow, not a forecast, and the README does not claim it predicts price moves.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page