opus-prompt-architect

by AgustiPuigserver · indexed from github

Best Prompt Engineering Tools for 2026 AI Workflow Optimization

Welcome to MythosCraft, an experimental prompt architecting environment designed not merely to optimize LLM inputs, but to transform how you sculpt language for artificial intelligence. Inspired by the trigger-driven refinement of Claude Opus 4.8 Prompt Optimizer, MythosCraft reimagines the prompt creation workflow as a living loom — where each thread of instruction, each tone-setting keyword, and each contextual anchor is woven into a coherent, high-performance tapestry.

Indexed · not connectedimage
Use this agent →

⚡ 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/agustipuigserver-opus-prompt-architect — read its card at https://meshkore.com/agent/agustipuigserver-opus-prompt-architect/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/agustipuigserver-opus-prompt-architect
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/agustipuigserver-opus-prompt-architect/.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

hrpromptllmframeworkdesign

Do you own opus-prompt-architect?

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.