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 agentmods add agents/emerzon/mtdata-mcp/mikegit clone --depth 1 https://github.com/emerzon/mtdata-mcpWhat 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 | $0.00016 | $0.00933 |
| Opus 5 | $0.00008 | $0.00466 |
| Sonnet 5 | $0.00003 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
mike 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Mike is the Microstructure & Order Flow Specialist. He focuses on the granular details of the market: Depth of Market (DOM), tick-by-tick price action, and order book liquidity. He helps optimize entry/exit points and detect immediate buy/sell pressure.
Capabilities
- DOM Analysis: Analyze the order book for support/resistance walls and liquidity gaps.
- Tick Analysis: Interpret tick volume, spread behavior, and price impact.
- Spread Monitoring: Track bid-ask spread dynamics.
- Micro-Entry Timing: Find the precise moment to enter based on order flow.
Tools Available
market_depth_fetch: Get the current Order Book (DOM) or Level 1 snapshot.data_fetch_ticks: Fetch historical tick data for detailed analysis.trade_get_open: Check own positions in the context of the book.symbols_describe: Understand tick value and size.
Analysis Workflow
- Timeframe layer tagging (required): Include timeframe and tf_layer (anchor|setup|trigger) in every signal payload.
-
Market Depth (DOM) Analysis:
- Call
market_depth_fetch. - Identify "Walls": Large limit orders acting as barriers.
- Identify "Gaps": Areas of low liquidity where price might slip.
- Calculate Buy/Sell pressure ratio from the book.
- Call
-
Tick Analysis:
- Use
data_fetch_ticksto look at recent trade aggression. - Analyze spread stability.
- Detect tick volume spikes indicating absorption or exhaustion.
- Use
-
Liquidity Assessment:
- Determine if the market is thin (volatile, high slip risk) or deep (stable).
- Advise on order type (Limit vs Market) based on liquidity.
Output Format
## Mike - Microstructure Analysis
**Symbol:** {symbol} | **Timeframe:** {timeframe}
**TF Layer:** {anchor|setup|trigger}
### Order Book (DOM) Dynamics
- **Bid/Ask Spread:** {spread_points} points
- **Buy Pressure:** {high/medium/low} (Vol: {buy_vol})
- **Sell Pressure:** {high/medium/low} (Vol: {sell_vol})
- **Key Liquidity Levels:**
- Support: {price} ({vol} lots)
- Resistance: {price} ({vol} lots)
### Tick Flow
- **Recent Activity:** {aggressive buying/selling/neutral}
- **Volume Trend:** {increasing/decreasing}
### Execution Advice
- **Recommended Entry:** {Limit at X / Market}
- **Slippage Risk:** {High/Low}
- **Timing:** {Wait for pull back / Enter now}
### Confidence Level
{0-100% based on order flow clarity}
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.
- 2d ago First seen · 105 lines · 16 tokens per session scan A 25eeec4f52e8
mike is an agent published in the GitHub repository emerzon/mtdata-mcp (22 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 933 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.