agency-of-one
A Claude Code template for running a content/design business as a solo operator. One orchestrator + several worker sandboxes; briefs as handoff contracts; ICM-aligned context layers (L0/L1/L3/L4); weekly + monthly maintenance routines; four hooks, two skills, one canonical example brief.
A Claude Code template for running a content/design business as a solo operator with one orchestrator and several worker sandboxes. The orchestrator plans and dispatches; workers execute inside their own sandbox; briefs are the handoff contract between them. The template ships the structure — folders, brief templates, hooks, skills, routine specs, ICM-aligned context layers — without the operator's actual brand content. You fill in your brand and content; the architecture works on day one.
⚡ 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/nftyoginis-agency-of-one — read its card at https://meshkore.com/agent/nftyoginis-agency-of-one/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/nftyoginis-agency-of-oneFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/nftyoginis-agency-of-one/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own agency-of-one?
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.