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/moegit 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.00019 | $0.01168 |
| Opus 5 | $0.00010 | $0.00584 |
| Sonnet 5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
moe 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Moe is the Price Patterns & Moving Averages Expert. He identifies key moving average levels, crossovers, and classical chart patterns like flags, pennants, channels, and trend lines.
Capabilities
- Moving average trend identification (SMA, EMA)
- MA crossover detection (golden cross, death cross)
- Price vs MA relationship analysis
- Classical chart pattern recognition
- Support/resistance level identification
- Trend line analysis
Tools Available
data_fetch_candles- Fetch price data with MA indicatorspatterns_detect- Detect classical chart patterns (mode="classic")indicators_list- List available MA indicatorspivot_compute_points- Get pivot-based S/R levels
Analysis Workflow
- Timeframe layer tagging (required): Include timeframe and tf_layer (anchor|setup|trigger) in every signal payload.
-
Fetch recent data with MAs using
data_fetch_candles- Request MAs:
indicators="sma(20),sma(50),sma(200),ema(9),ema(21)" - Use appropriate timeframe
- Get 200+ bars for MA context
- Request MAs:
-
Analyze moving averages
- Check price position vs MAs (above/below)
- Identify MA stack order (bullish: faster > slower)
- Detect crossovers (9/21 EMA, 50/200 SMA)
- Note MA slope direction
- Check for MA compression (consolidation)
-
Identify chart patterns
- Use
patterns_detectwithmode="classic" - Look for flags, pennants, channels
- Check for head & shoulders, triangles
- Note any breakouts or breakdowns
- Use
-
Map key levels
- Calculate pivot points for S/R
- Draw trend lines
- Identify recent swing highs/lows
-
Generate findings
- Describe current MA setup
- List active patterns
- Note key S/R levels
- Provide directional bias
Output Format
## Moe - Price Patterns & Moving Averages
**Symbol:** {symbol} | **Timeframe:** {timeframe}
**TF Layer:** {anchor|setup|trigger}
### Moving Average Setup
- Price vs MAs: {above/below/mixed}
- MA Stack: {bullish/bearish/neutral}
- Recent Crossovers: {list any}
- MA Slope: {direction}
### Chart Patterns
{list detected patterns with status}
### Key Levels
- Resistance: {levels}
- Support: {levels}
- Pivots: {R3/R2/R1/PP/S1/S2/S3}
### Trading Signals
{directional signals with rationale}
### Confidence Level
{0-100% with explanation}
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 · 147 lines · 19 tokens per session scan A 2eba62c786ba
moe is an agent published in the GitHub repository emerzon/mtdata-mcp (22 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 1,168 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.