The best person on your team, on every machine — executive brief

modiqoEXECUTIVE BRIEF01 / 14

The best person on your team, on every machine.

How the way your expert does a job becomes a Play anyone can run.

curl -fsSL https://getrote.dev/playoffs/install.sh | sh
Start with why a better model is not enough. ↓
modiqoTHE TRAP02 / 14

A better model does not make a better team.

Give the same model to an expert and to a beginner. The expert gets the right answer. The beginner gets a confident one.

So the question is not which model. It is who is steering. ↓
modiqoTHE ARITHMETIC03 / 14

How many of your people are experts at the job in front of them?

In most teams, a few. Everyone else asks them, waits for them, or guesses.

8 who know how · 92 who ask them

And the few do not stay forever. ↓
modiqoTHE LEAK04 / 14

When the expert leaves, the way leaves with them.

What stays behind is scattered. A chat thread. Half a wiki page. Someone’s memory of how it went last time.

Unless the way was written down while it happened. ↓
modiqoWHAT ROTE DOES05 / 14

Rote watches your expert steer the agent.

The expert corrects the agent until the job is done right, in the fewest tokens. Rote records the path that worked.

/play the agents spent $1,400 overnight. why?
AGENT✗compared model prices
YOU›it’s never the model. group the calls by tool.
AGENT✓fetch-invoice: 3,100 calls, every one a 404
YOU›cap retries at 3.
AGENT✓with the cap: $9
That path is the expertise. Rote keeps it. ↓
modiqoTHE PLAY06 / 14

The expertise becomes a Play.

The steps that worked, kept as one file at one link, saved to your private hub.

What is behind that link? ↓
modiqoTHE FILE07 / 14

Behind the link is code, not a chat.

Every step written down, in order. Read-only by declaration. Keys by name, never inside. It runs on any model, on any machine, the same steps every time.

≡×MAIN.TS · PRIYA/[email protected]
name: overnight-billtags: [effect-read-only]adapter_credentials: OPENAI_ADMIN_KEY   # by name, stays on your machinesteps:  sessions:   process.exec   # read the harness logs  by_tool:    process.exec   # group the calls, depends_on: sessions  spend:      adapter/openai-admin   # usage api, read scope  retry_cap:  process.exec   # grep max_retriesfingerprint: api_7QbFkzR2nYtWm4Lp   # checked before every run
SAME STEPS · SAME ORDER · YOUR OWN DATAREAD-ONLY BY DECLARATIONKEYS NEVER INSIDE
A file like that can go anywhere. ↓
modiqoTHE HUB08 / 14

One link carries it to everyone.

A teammate opens the link and runs the expert’s steps with their own keys. No expert needed. The community gets it only if you publish it.

And every run after the first is different in one way. ↓
modiqoTHE RESULT09 / 14

Same steps. Zero reasoning tokens.

The expert paid for discovery once. Every run after replays the same steps on that person’s own data and keys, with no reasoning bill.

21,400tokens, once, while the expert steered
0reasoning tokens on every run after
samesteps, in the same order, every time
Do that for every job your experts know, and something builds up. ↓
modiqoTHE MOAT10 / 14

Expertise stops leaving. It compounds.

Every steered run adds a Play to the hub. Every new hire runs them on day one. The hub is private, versioned, and yours.

every steered run adds a row · every new hire runs them on day one

It takes less time to start than you think. ↓
modiqoGETTING STARTED11 / 14

Any domain. Any model. Any machine. Any cloud.

Under a minute to start. Install Rote, then ask your agent to explore with Play. It works with the agents your team already uses.

curl -fsSL https://getrote.dev/playoffs/install.sh | sh

then, in your agent

/play the agents spent $1,400 overnight. why?

works with claude code · codex · cursor · kimi · hermes · pi

You are not the first. Hundreds of Plays are already public. ↓
modiqoTHE COMMUNITY12 / 14

See what the world is already teaching.

Every public Play, read from its own file and ranked live: what they reach, who made them, what the first run cost.

OPEN THE CATALOG →
Want to see one come to life? ↓
modiqoTHE STORY13 / 14

Watch a Play be born.

Fourteen beats on one landscape, with the real commands beside each one.

PLAY THE STORY →
  1. 01the loop
  2. 02every run from zero
  3. 03explore, then compile
  4. 04rote
  5. 05a workspace
  6. 06talking to the world
  7. 07the graph
  8. 08steering
  9. 09the goal
  10. 10a play is born
  11. 11portable
  12. 12it travels
  13. 13what you get
  14. 14the catalog
Then keep one of your own. ↓
modiqoNEXT14 / 14

Install. Ask. Keep.

One command. One question to your agent. One Play in your hub by the end of the day.

curl -fsSL https://getrote.dev/playoffs/install.sh | sh

then, in your agent

/play the agents spent $1,400 overnight. why?

works with claude code · codex · cursor · kimi · hermes · pi

modiqo.ai · thank you
Back to Modiqo ↖