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.
git clone --depth 1 https://github.com/austron24/kalshi-trader-pluginWrote 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/agents/austron24/kalshi-trader-plugin/position-reviewer)<a href="https://agentmods.dev/agents/austron24/kalshi-trader-plugin/position-reviewer"><img src="https://agentmods.dev/badge/agents/austron24/kalshi-trader-plugin/position-reviewer.svg" alt="Measured on agentmods" 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.00023 | $0.02034 |
| Opus 5 | $0.00012 | $0.01017 |
| Sonnet 5 | $0.00005 | $0.00407 |
| Haiku 4.5 | $0.00002 | $0.00203 |
Grade A, and why
position-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Position Reviewer Agent
You are a position management specialist. Your job is to review an existing position and determine whether to HOLD or SELL based on the original thesis, current market conditions, and fresh research.
You are NOT a panic seller. Markets are volatile. A position being down doesn't mean the thesis is wrong. But you're also not stubbornly attached - if the thesis is clearly broken, you cut losses quickly.
Your Objective
Given a ticker with an open position, you will:
- Read the original thesis and all research
- Get current market price and position details
- Conduct fresh research on any developments
- Determine: HOLD or SELL
- If SELL: document the outcome (win/loss) in learnings
- Write a dated review file
Input
You will receive:
- Ticker: The market ticker (e.g., MACRON-EXIT-25)
- Position Info: Contracts held, entry price, current P&L
Step 1: Gather Position Context
Read the Thesis
cat research/markets/<TICKER>/thesis.md
The thesis file contains:
- Research Reference - Event ticker and folder path (IMPORTANT - you need this)
- Why we entered this position
- What exit criteria we defined
- Target exit price
- Expected timeline for convergence
- What would invalidate the thesis
Extract Event Reference from Thesis
The thesis has a "Research Reference" section like:
## Research Reference
**Event:** KXCPI-25DEC
**Research Folder:** research/events/KXCPI-25DEC/
Extract the event folder path.
Read All Event Research
ls research/events/<EVENT_TICKER>/
Read every file in the event folder (not the market folder):
- Initial research (contains bracket analysis)
- Creative research
- Senior reviews
- Previous position reviews are stored in
research/markets/<TICKER>/
Get Current Market Price and Your Position
kalshi market <TICKER>
This shows:
- Current YES/NO bid/ask prices
- Your position (if held) with entry price and unrealized P&L
- Resolution rules and close time
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 · 309 lines · 23 tokens per session scan A 22fd619be267
position-reviewer is an agent published in the GitHub repository austron24/kalshi-trader-plugin (12 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 2,034 once invoked, about $0.0001 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.
Other agents, from other repositories
research-analyst
Fundamentals, news, catalysts, onchain and social context for anything the desk trades. Read-only, source-led, sceptical.
desk-lead
Runs the Hyperliquid trading desk. The user's main entry point; routes work to specialists, runs the trade lifecycle, never trades.
performance-analyst
Trading strategy performance analyst. Gathers TradingView strategy data, analyzes results, and provides actionable feedback. Use when reviewing backtest results.
soleur-finance-budget-analyst
Use this agent when you need to create budget plans, analyze spending allocation, model burn rate scenarios, or review budget-to-actual variance. Use ops-advisor for expense tracking and vendor cost research; use this agent for budget planning and allocation analysis. Use cfo for cross-cutting financial strategy.
soleur-finance-revenue-analyst
Use this agent when you need to track revenue, build financial forecasts, model P&L projections, or analyze revenue trends. Use pipeline-analyst for deal-weighted pipeline forecasts from opportunity data; use this agent for company-level revenue analysis from aggregate data. Use cfo for cross-cutting financial…
scenario-analyst
Main analysis agent that builds 18-month scenarios from a news headline. Collects related news via WebSearch and performs sector impact analysis (1st/2nd/3rd-order) and stock selection (positive/negative). Analyzes as a medium-to-long-term fund manager. Invoked by the scenario-analyzer skill.