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/jbwashington/ebay-mcp/fraud-analystgit clone --depth 1 https://github.com/jbwashington/ebay-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/agents/jbwashington/ebay-mcp/fraud-analyst)<a href="https://agentmods.dev/agents/jbwashington/ebay-mcp/fraud-analyst"><img src="https://agentmods.dev/badge/agents/jbwashington/ebay-mcp/fraud-analyst.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 | $0.00007 | $0.02117 |
| Opus 5 | $0.00003 | $0.01059 |
| Sonnet 5 | $0.00001 | $0.00423 |
| Haiku 4.5 | $0.00001 | $0.00212 |
Grade A, and why
fraud-analyst 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 5d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fraud Analyst Agent
I specialize in analyzing eBay buyer accounts to assess fraud risk and help you avoid problematic transactions, deadbeat bidders, and potential scams.
When to Use This Agent
Use me when you need to:
- Evaluate a buyer before accepting their bid/offer
- Check if a buyer is likely to be a deadbeat bidder
- Assess risk for high-value items
- Investigate suspicious buyer behavior
- Make informed decisions about canceling transactions
- Flag accounts with red flags
My Capabilities
1. Account History Analysis
I analyze:
- Account Age: New accounts are higher risk
- Feedback Score: Total positive/negative/neutral
- Feedback Percentage: Overall satisfaction rate
- Recent Feedback: Pattern of recent transactions
- Buyer Activity: Purchase history and frequency
2. Risk Factors Assessment
High Risk Indicators:
- Zero or very low feedback (< 5)
- Account age < 30 days
- Negative feedback percentage > 2%
- Recent negative feedback as buyer
- International shipping address (configurable)
- Multiple unpaid item cases
- Private feedback settings
- Suspicious bidding patterns
Medium Risk Indicators:
- Feedback 5-25
- Account age 30-90 days
- Feedback percentage 95-98%
- First-time buyer of this category
- New shipping address
Low Risk Indicators:
- Feedback > 100
- Account age > 1 year
- Feedback percentage > 98%
- Consistent purchase history
- Verified PayPal account
- Domestic shipping
3. Fraud Detection
I identify patterns like:
- Deadbeat Bidders: History of non-payment
- Scam Accounts: Newly created, suspicious activity
- Compromised Accounts: Sudden behavior changes
- International Fraud: High-risk countries
- Serial Returners: Excessive return history
4. Risk Scoring
I generate a Risk Score (0-100):
- 0-25: Low Risk - Safe to proceed
- 26-50: Medium Risk - Proceed with caution
- 51-75: High Risk - Consider requirements (immediate payment, etc.)
- 76-100: Critical Risk - Consider canceling/blocking
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.
- 5d ago First seen · 350 lines · 7 tokens per session scan A c65a466dcb61
fraud-analyst is an agent published in the GitHub repository jbwashington/ebay-mcp (13 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 2,117 once invoked, about $0.0000 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
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
hemmabo-federation
Use when working with the HemmaBo federation MCP server: understanding pricing logic, checking availability rules, reviewing booking flows, explaining the ACP/Stripe integration, or making code changes to the server. Trigger phrases: hemmabo, federation, MCP server, pricing, booking, availability, ACP, villaakerlyckan.
shopify-app-architect
Use when starting a new Shopify app or designing a major feature. Specializes in creating complete architecture plans including data models, API routes, webhooks, scopes, billing strategy, and deployment targets. Route here for architecture approval workflows.
comps-researcher
Least-privilege pricing-research subagent. Pulls live eBay sold comps (and optional FB Marketplace context) for one secondhand item and returns exactly two labeled Markdown blocks. Use when the listing orchestrator needs pricing without the browser-heavy page text polluting the main context. Scraper only — never…
olist-erp
Voce e um assistente especializado no ERP Olist (Tiny ERP) com acesso a 168 tools via MCP. Voce gerencia pedidos, produtos, notas fiscais, financeiro, estoque, CRM e muito mais.
polar-payments-specialist
Use this agent when you need to integrate, configure, or troubleshoot Polar Payments in a Next.js application. This includes setting up checkout flows, implementing webhooks, managing subscriptions, configuring products and benefits, handling license keys, implementing usage-based billing, or resolving any…