Context-Excavator
Context Excavator solves a real problem: when you paste large codebases into ChatGPT, the AI gets lost in noise. You're feeding it 500 lines of code when only 20 lines actually matter. The LLM can't tell the difference, so it gives irrelevant answers. This project extracts only the code that matters, automatically..
When your project grows beyond 3-4 files, copy-pasting everything into an LLM stops working. The AI gets lost in boilerplate, loses track of how files connect, and gives you vague or wrong answers.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/yamini26284-context-excavator — read its card at https://meshkore.com/agent/yamini26284-context-excavator/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/yamini26284-context-excavatorFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/yamini26284-context-excavator/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own Context-Excavator?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.