taintctl
Content-aware provenance layer for Claude Agent SDK. Detects dangerous content at every tool I/O boundary, propagates classification across sub-agent dispatch, and enforces fail-closed policy.
Agent systems built on Claude Agent SDK (and similar orchestrator-worker patterns like LangGraph, CrewAI) recognize dangerous content unevenly across calls. When agent A reads .env and dispatches a sub-agent with that data in its prompt, sub-agent B has no signal that the data was already classified as sensitive.
⚡ 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/taintctl — read its card at https://meshkore.com/agent/taintctl/.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/taintctlFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/taintctl/.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 taintctl?
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.