Training
Certification Leadership Frameworks Agentic for Business
Community Keynotes Retreat Blog Book A Consultation
Protocol 03 of 18 · Track, Mindset · How we think

Agents, the folder is the agent

An agent is not a magical entity. It is a folder of markdown files plus a prompt. Structure the folder well and the agent works. Structure it badly and it does not.

Protocol 02 The stack, Claude plus GitHub plus Vercel plus Supabase All 18 Protocol 04 Cataloguing, folder structures for agentic development
Why this matters

The pain it
solves

Agent is the most overused word in AI right now. Most people imagine a black-box autonomous robot. That misunderstanding is expensive. It makes people scared of agents (too magical), disappointed by them (not magical enough), or sold things that are not really agents.

Once you see that an agent is a folder, the fear and mystique go away. You can read it. Edit it. Copy it. Hand one to a teammate. Build a new one in fifteen minutes.

The teaching

What this
actually is

What is actually in the folder

An agent is not a magical entity. It is a folder on your computer that contains three kinds of file. The LLM is the same Claude everyone else uses. The folder is what makes Claude behave like a specialist.

  • Role definition
    A markdown file (often called AGENT.md or named after the agent) that tells the LLM who it is, what it does, what to avoid, and what tone to use. The shortest version of a job description.
  • Context
    More markdown the agent reads to do its job. Brand voice for the writer. Open epics for the PM. Current test plan for QA. Anything the agent should know before starting.
  • Skills
    Reusable prompts the agent invokes for specific tasks. Slash commands. Short, named playbooks. The verbs of the agent.

Why the folder framing matters

Once you see that an agent is a folder, the fear and the mystique both go away. You can read it. Edit it. Copy it. Hand one to a teammate. Make a new one in fifteen minutes by copying an existing one and changing the role.

The opposite framing, the magic-black-box framing, is what makes people scared of agents, disappointed in them, or sold things that are not really agents at all. If you cannot open the folder, you do not own the agent.

The eight agents you walk out with

You leave the retreat with eight agents on your Mac Mini. Four on the build team, four on the go-to-market team. All eight are folders you can open, read, and modify.

  • Build team
    PM (plans), Developer (builds), QA (tests), DevOps (ships).
  • Go-to-market team
    Writer (drafts), Designer (visuals), Web Publisher (publishes), Email Marketer (campaigns).
Try it yourself 20 minutes

Read, edit, and rerun one agent in 20 minutes

If you have the IL agent team installed (from the retreat or the template repo), use the writer agent. If not, copy any agent's folder from the template into a new project to follow along.

  1. Step 01
    Open the agent's folder

    In your terminal, cd into .claude/agents/writer (or wherever your agent lives). Run ls. You will see a small set of markdown files. Open them in your editor.

  2. Step 02
    Read the role definition

    Open the file that defines the agent (typically AGENT.md, writer.md, or a file with frontmatter). Notice how short and specific it is. The whole agent is this paragraph plus a few skills.

  3. Step 03
    Run the agent on a small prompt

    In Claude Code, ask the writer agent: "Write a 50-word intro for an Infinite Leverage retreat." Save the output.

  4. Step 04
    Edit the role definition

    Change one line in the role file: tone ("be playful, use short sentences") or focus ("always end with a question"). Save.

  5. Step 05
    Run the same prompt again

    Ask the same agent the same prompt. The output will be visibly different. Same Claude, different folder, different result.

Outcome

You have seen, with your own eyes, that the agent is the folder. Same model, different folder, different specialist. The black-box mystique is gone for good.

Official resources

Straight from
the source

What you walk out with

By the end of this
protocol

At the retreat

You learn it by
doing it

You open one of the eight agents, change its role definition, run it twice on the same prompt, and watch the same model produce two different outputs because the folder told it to.

Connects to

Other protocols this
compounds with

← Previous, Protocol 02 Next, Protocol 04 →