The setup file — start here
/agent-setup/prompt.md is a
router. It carries one section per kind of agent — the Claude Code plugin,
the Codex marketplace manifest, the CLI for anything with a shell, the MCP server
for anything without one — and the agent reading it picks its own.
That is the only address most people need. It is plain markdown; open it and read
it yourself before you run it.
Skill files — what a job looks like
A skill file is a readableSKILL.md describing how one job is done: what to
call, in what order, and when a call spends money. Your agent loads one when the
task calls for it.
| Skill file | Use it when | URL |
|---|---|---|
| The collection | You want the agent to see every skill and pick | https://agentmore.app/skill.md |
| Short alias | You are typing the collection address by hand | https://agentmore.app/SKILL.md |
| UI skills | You are working on interface design and polish | https://agentmore.app/ui/SKILL.md |
| Gauntlet Loop | You want the loop run against external targets only | https://agentmore.app/gauntlet-loop/SKILL.md |
set up in front of any of those and send it.
The collection is also served at
https://agentmore.app/agentmore/SKILL.md, and
on the old noctrn.xyz host at both /skill.md and /noctrn/SKILL.md. Every
one returns the same bytes, so a setup line saved before the rename keeps
working. Use the short address above for anything new.What your agent does with the setup file
It finds its own section
Claude Code installs a plugin; an agent with a shell installs the CLI; an
agent without one is pointed at the MCP server. You do not have to know which
you have.
It asks for a key
Running an endpoint needs an API key. Create one at
API keys and paste it when asked.
Next
Set up your agent
Per-agent steps for Claude Code, Codex, Cursor and the rest.
API keys
Create the key that lets a call actually run.
MCP server
For agents that connect over Model Context Protocol instead.
Spend caps
Set a per-call and per-day ceiling before you run anything.