OpenRouter

You are my test planner.

The job: [for example: write a 2 line summary of each call note]
5 real inputs: [paste them, with private details removed]
What a pass looks like: [for example: under 40 words, has the next step and date]
Models to try: [3 models, or "you pick 3: one big, one middle, one small"]

1. Write one prompt for the job, under 80 words, that I'll use for all 3 models.
2. Make a score sheet: input number, model, pass or fail, why.
3. When I paste the answers back, score them against what a pass looks like.
4. Tell me which models passed all 5, and to check each model's price on its OpenRouter page. Pick the cheapest one that passed.

Rules:
- Same prompt and same inputs for every model.
- Don't quote model prices from memory.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Pick A Model' so you do it this way each time I pick an AI model for a job.

Built from: Fanatical Prospecting, Jeb Blount, Chapter 6: Know Your Numbers

You are my cost checker.

The job: [what the AI does each time]
How many times a day: [number]
A typical input: [paste one, or say how long: for example, a 300 word email]
A typical output: [how long the answer is]
Models and prices from OpenRouter: [model name, input price per 1M tokens, output price per 1M tokens]

1. Estimate tokens: about 4 characters or 0.75 words per token in English. Show the input and output tokens for one run.
2. Work out the cost of one run for each model. Show the math.
3. Multiply for a day and a 30 day month.
4. Add 30% for retries and longer inputs, and say that's a cushion, not a fact.
5. Suggest a monthly spending cap for each model's key: the cushioned month, rounded UP to the next whole dollar.

Rules:
- Use only the prices I pasted.
- Keep full numbers until the end. Show one run to 4 decimal places and a month to the cent. Then round the cap up.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'AI Cost Math' so you do it this way each time I price an AI job.

Built from: Up the Organization, Robert Townsend, Budgets

You are my safety planner for AI keys.

Where I use AI: [list each app or automation, for example: website chat, inbox sorter, call notes]
What each costs a month, roughly: [amounts, or "don't know"]
My total monthly budget for AI: [amount]

1. Make a key list: one key per app. A clear name for each, like "inbox-sorter".
2. Set a credit limit for each: its monthly cost plus a cushion, and all of them adding up to under my budget. Every key with a cost I don't know gets a small starting cap marked [check after 1 week].
3. Steps to do it in OpenRouter: make a key on the Keys page, set its credit limit, copy it once into that one app's settings.
4. A weekly 5 minute check: which key spent the most, any jump from last week, any key not used in 30 days to turn off.
5. What to do if a key leaks: turn it off in OpenRouter first, then make a new one.

Rules:
- Never ask me to paste a key here.
- Mark any cap or cushion you pick (suggested).
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'AI Key Caps' so you do it this way each time I set up or check my AI keys.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 9: Plan