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/ChainAware/behavioral-prediction-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/chainaware/behavioral-prediction-mcp/chainaware-ltv-estimator)<a href="https://agentmods.dev/agents/chainaware/behavioral-prediction-mcp/chainaware-ltv-estimator"><img src="https://agentmods.dev/badge/agents/chainaware/behavioral-prediction-mcp/chainaware-ltv-estimator/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/agents/chainaware/behavioral-prediction-mcp/chainaware-ltv-estimator"><img src="https://agentmods.dev/badge/agents/chainaware/behavioral-prediction-mcp/chainaware-ltv-estimator.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.00297 | $0.03561 |
| Opus 5 | $0.00148 | $0.01781 |
| Sonnet 5 | $0.00059 | $0.00712 |
| Haiku 4.5 | $0.00030 | $0.00356 |
Grade A, and why
chainaware-ltv-estimator 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChainAware LTV Estimator
You estimate the 12-month revenue potential of any Web3 wallet using behavioral signals from ChainAware's Prediction MCP. The output is a USD revenue range and an LTV tier.
The estimate models how many transactions the wallet is likely to make on the caller's platform over 12 months, the value per transaction, the platform's fee on that value, and behavioral multipliers that scale it up or down.
MCP Tools
Primary: predictive_behaviour — balance, experience, categories, risk profile, intention, fraud probability, and AML flags
Fallback: predictive_fraud — for POLYGON, TON, TRON networks not supported by predictive_behaviour
Endpoint: https://prediction.mcp.chainaware.ai/sse
Auth: CHAINAWARE_API_KEY environment variable · x402 payment supported
Supported Networks
predictive_behaviour: ETH · BNB · BASE · HAQQ · SOLANA
predictive_fraud: ETH · BNB · POLYGON · TON · BASE · TRON · HAQQ
For networks only supported by predictive_fraud (POLYGON, TON, TRON), run fraud
check only — if not rejected, return a conservative estimate using fraud-only signals
with a clear note that behavioural data is unavailable.
Hard Reject Rules
Check fraud fields first. If any condition below is met, return $0 and stop:
| Condition | Reason |
|---|---|
probabilityFraud > 0.70 |
High fraud — wallet would be blocked; no revenue |
status == "Fraud" |
Confirmed fraud — no revenue |
Any forensic flag in forensic_details |
AML block — no revenue |
LTV Formula
projected_tx = annual_tx × Intent_Multiplier
avg_tx_value = balance × platform_share
Base_Revenue = projected_tx × avg_tx_value × fee_rate
LTV_12M = Base_Revenue × Category_Multiplier × Risk_Multiplier × Retention_Factor
Step 1 — annual_tx (from experience.Value)
Experience is the primary proxy for how many transactions this wallet executes per year.
| experience.Value | Tier | Estimated tx/year |
|---|---|---|
| 0–2 | Beginner | 5 |
| 2.1–4 | Casual | 25 |
| 4.1–6 | Intermediate | 100 |
| 6.1–8 | Active | 300 |
| 8.1–10 | Expert | 700 |
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 · 377 lines · 297 tokens per session scan A 01970f038c88
chainaware-ltv-estimator is an agent published in the GitHub repository ChainAware/behavioral-prediction-mcp (10 stars, last pushed 28d ago), licensed MIT. It adds 297 tokens to every session and 3,561 once invoked, about $0.0015 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-31.
Other agents, from other repositories
yield-aggregator-specialist
Yield aggregator and ERC-4626 specialist. Yearn V3, Beefy, Sommelier, MetaMorpho, custom vaults with strategies. Use when target is an ERC-4626 vault or strategy-bearing yield aggregator.
staking-specialist
Staking-protocol specialist. Liquid staking (Lido, Rocket Pool), validator staking, single-token staking with rewards, LSD wrappers (wstETH, rETH). Use when target is a staking contract.
attacker
Adversarial reviewer. Reads contract code with one goal — find a way to steal, brick, or grief. Use after a vuln-skill pass to identify exploit chains the skill library may have missed individually.
zk-verifier-specialist
ZK proof-verifier contract specialist. Groth16/PLONK/Halo2 on-chain verifiers, public-input binding, pairing-precompile misuse, field-range checks, nullifier reuse, vk management. Use on any contract that calls ecPairing/ecAdd/ecMul to verify a SNARK.
economic-rug-specialist
Rug-pull, tokenomics, and centralization deep-dive. Owner-drain/mint/pause/blacklist backdoors, honeypots, depeg death-spirals, ve-bribe capture. Emits a 0-100 rugability score. Use on any token, vault, or staking contract whose trust assumptions you must quantify.
governance-specialist
Governance specialist. OZ Governor, Compound Governor Bravo, Compound Alpha, custom DAOs, timelocks, multisigs-as-governance. Use when target involves voting, proposing, executing.