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.
npx skills add target1m/traderspy-mcp --skill position-checkgit clone --depth 1 https://github.com/target1m/traderspy-mcpWrote 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/target1m/traderspy-mcp/position-check)<a href="https://agentmods.dev/skills/target1m/traderspy-mcp/position-check"><img src="https://agentmods.dev/badge/skills/target1m/traderspy-mcp/position-check/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/target1m/traderspy-mcp/position-check"><img src="https://agentmods.dev/badge/skills/target1m/traderspy-mcp/position-check.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.00190 | $0.01455 |
| Opus 5.5 | $0.00076 | $0.00582 |
| Sonnet 5.5 | $0.00038 | $0.00291 |
| Haiku 4.5 | $0.00019 | $0.00145 |
Grade B, and why
position-check scanned grade B with 1 finding 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 14d 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
- Never tell the user to close, hold, add, hedge, move a stop or change leverage. Present How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A position check answers, in order: how much room is left before this position is taken away (liquidation), how much before the user's own plan says it is wrong (stop), what the chart and the derivatives market are doing around it, and who else is positioned the same way. Report those facts with numbers. The decision — hold, trim, close, add — belongs to the person whose money it is.
Inputs
The position always comes from the user. TraderSpy has no account tool: it cannot read a balance or an open position on any exchange, so never offer to "check the account".
Ask for whatever is missing among side, entry, leverage (and stop / target / the exchange's
liquidation price if they have them). Size is optional — the analysis works in percentages. The
current price is the price that get_technical_indicators returns.
Map the symbol to Binance naming for the data tools: BTC → BTCUSDT, kPEPE → 1000PEPEUSDT,
xyz:AVGO → AVGOUSDT.
Calls per position (keep it to what matters)
get_technical_indicators—intervals: ["1h","4h","1d"],indicators: ["rsi","macd","ema", "atr","adx","supertrend","levels"], and the coins assymbols(up to three in ONE call; each coin's read is its own entry indata[]). This gives the trend on three timeframes, ATR for stop sanity and the nearest levels.get_derivatives— up to five coins in ONE call for all positions at once. Funding is a cost or an income for this position; the OI regime says whether the move is being funded.get_positions—symbol,status: "open",limit: 20. Optional; skip on a tight quota. Tells you whether tracked top traders are on the same side.
Three positions ≈ 1 + 1 (+3) calls. If the quota is tight, skip step 3: technicals and derivatives for every position are still two calls.
The math (show it, briefly)
- P&L % on margin = (mark − entry) / entry × leverage, sign-flipped for shorts; P&L % on price = the same without leverage. State both when leverage > 1.
- Distance to liquidation = |liq − mark| / mark. With no liquidation price from the user, approximate: ≈ 100 / leverage % minus a maintenance buffer (say it is approximate; cross margin makes the real distance depend on the whole account).
- Distance to stop = |stop − mark| / mark, and stop distance in ATRs = |stop − mark| / ATR(14) on the 4h. Under 1 ATR means the stop sits inside normal noise for that timeframe.
- Funding per day ≈
funding.ratePct× 3 on notional; positive rate costs longs and pays shorts.
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.
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.
- 14d ago Changed · +1 lines c6a91a367631
- 23d ago Changed · -6 lines · -6 tokens per session c908dd9db12c
- 1mo ago First seen · 96 lines · 196 tokens per session scan B 1eef2d671386
position-check is a skill published in the GitHub repository target1m/traderspy-mcp (2 stars, last pushed 6d ago), licensed MIT. It adds 190 tokens to every session and 1,455 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other skills, from other repositories
markettrace-agent-feed
A workflow for an AI agent using the MarketTrace agent-feed MCP tools. The feed reports facts and measured history, not predictions — every interpretation is yours.
derivatives-trading-portfolio-margin
Binance Derivatives-trading-portfolio-margin request using the Binance API. Authentication requires API key and secret key. Supports testnet and mainnet.
derivatives-trading-usds-futures
Binance Derivatives-trading-usds-futures request using the Binance API. Authentication requires API key and secret key. Supports testnet and mainnet.
spot
Binance Spot request using the Binance API. Authentication requires API key and secret key. Supports testnet, mainnet, and demo.
assets
Binance Assets request using the Binance API. Authentication requires API key and secret key.
derivatives-trading-coin-futures
Binance Derivatives-trading-coin-futures request using the Binance API. Authentication requires API key and secret key. Supports testnet and mainnet.