What is market-incident-monitoring?

A monitoring guide for lending markets and related financial products in decentralised finance, or DeFi. It retrieves market conditions, vault information, and recorded incidents from Philidor tools.

It is for market overviews, lending-market research, vault incident checks, and protocol security history.

It keeps different questions separate, such as overall market size, one market's rates, and incidents affecting that market. It also requires reported identifiers and figures rather than guesses.

market-incident-monitoring — Skill for Cursor by Philidor-Labs

Install

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.

Any agent

npx skills add Philidor-Labs/philidor-mcp --skill market-incident-monitoring

Clone the repo

git clone --depth 1 https://github.com/Philidor-Labs/philidor-mcp

Made for: Cursor.

Or install philidor, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/philidor-labs/philidor-mcp/market-incident-monitoring/github.svg)](https://agentmods.dev/skills/philidor-labs/philidor-mcp/market-incident-monitoring)

Your own site

<a href="https://agentmods.dev/skills/philidor-labs/philidor-mcp/market-incident-monitoring"><img src="https://agentmods.dev/badge/skills/philidor-labs/philidor-mcp/market-incident-monitoring/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/philidor-labs/philidor-mcp/market-incident-monitoring"><img src="https://agentmods.dev/badge/skills/philidor-labs/philidor-mcp/market-incident-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 830 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00048	$0.00830
Opus 5.5	$0.00019	$0.00332
Sonnet 5.5	$0.00010	$0.00166
Haiku 4.5	$0.00005	$0.00083

Measured 16d ago against content hash 9d6c32c9129c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

market-incident-monitoring 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 16d 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.

skills/market-incident-monitoring/SKILL.md · 41 lines

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Market and incident monitoring

Three different calls cover “the market”. Do not swap them.

Question	Tool
Platform-wide vault TVL, vault count, risk mix, TVL by protocol	`get_market_overview` (no arguments)
A list of lending markets (Aave spoke, Morpho Blue pair, Kamino K-Lend, and similar)	`list_markets`
One market’s reserves, rates, utilization, tiers	`get_market` with `marketId`
Events on one market (incidents, bad debt, liquidation cascades)	`get_market_events` with `marketId`
Vaults with a critical incident in the last 365 days	`list_vaults_with_incidents` (no arguments)
One protocol’s audits and security history	`get_protocol_info` with `protocolId`

The hosted server is https://mcp.philidor.io/api/mcp. Quote market ids, vault ids, and counts from the tool result. Never invent an incident, a date, or a TVL.

Lending markets

Call list_markets with the filters the user named. protocol is aave, spark, compound, morpho, or kamino. version is v3, v4, or klend. Aave V4 is protocol=aave and version=v4 (aave-v4 is an accepted alias). chain is an integer id or a slug. sortBy is total_supplied_usd, total_borrowed_usd, reserve_count, or name. limit is 1–100, default 20.
Pass a marketId from that response into get_market. Spoke ids look like aave-v4-1-main. Composed Aave V4 hub parents look like aave-v4-1-hub-global-dollar. If get_market does not serve a hub id, open a spoke id returned under that hub. Do not invent a spoke id.
Call get_market_events for “what happened on this market”. limit is 1–100, default 20. Hub ids union the spoke feeds. This is not get_market_overview.

Vault incidents and protocols

list_vaults_with_incidents lists vaults with a critical incident in the last 365 days (severity Critical, or incident_severity major), sorted by TVL descending, then by recency. It has no filters. Say that window in the answer. It is not a full lifetime history and not “every warning”.
For a protocol the user named, call get_protocol_info. Live protocol ids include aave, morpho, spark, compound, yearn, beefy, uniswap, nest, maple, and kamino. Aave V4 is under aave. Use an id the user named only if it matches this set or an id a previous tool returned. Otherwise say the id is not in the tool’s protocol list and read philidor://supported-protocols.
For one vault’s own events, use get_vault (see the vault due diligence skill). Do not claim a vault is clean because it is missing from the 365-day critical list.

Read the full file on GitHub · 41 lines

Changes

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.

16d ago First seen · 41 lines · 48 tokens per session scan A 9d6c32c9129c

Subscribe to this mod's changes

market-incident-monitoring is a skill published in the GitHub repository Philidor-Labs/philidor-mcp (5 stars, last pushed 16d ago), licensed MIT. It adds 48 tokens to every session and 830 once invoked, about $0.0002 per session on Opus 5.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-10-01.

Finance and fintech Web3 and blockchain aave ai-tools claude crypto defi ethereum

market-incident-monitoring

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Market and incident monitoring

Lending markets

Vault incidents and protocols

What this file has done since we first saw it

Other skills, from other repositories

trading-solana

pump-swarm

copy-trading

trading-evm

whale-tracking

acp