3tears-agent-knowledge
Governed-knowledge retrieval + injection for LLM agents -- concepts, playbook entries, three-scope shadow merge, and before_model middleware
Homes the playbook-entry / concept collections (over the platform RBAC proxy), the KnowledgeIntegration wiring, and the create_agent before_model injection middleware, on top of the shared three-scope shadow-merge authority in threetears.knowledge (core). It lives in its own package because the collections depend on threetears.agent.acl, which core cannot depend on.
⚡ 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/pace-3tears-agent-knowledge — read its card at https://meshkore.com/agent/pace-3tears-agent-knowledge/.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/pace-3tears-agent-knowledgeFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/pace-3tears-agent-knowledge/.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 3tears-agent-knowledge?
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.