/cost
Know what a feature really costs before you build it
Break down a feature or vendor across money, build time, learning curve, lock-in, and ongoing maintenance.
What it does
Vendors advertise the free tier, not the bill you get at 10,000 users. /cost makes your agent lay out what a feature or service actually costs across five axes: money, build time, learning curve, lock-in, and ongoing maintenance, in plain language, before you commit.
It answers the questions pricing pages dodge: where the free tier actually ends, what switching away would take later, and how much of your week this thing will quietly eat once it's live.
What it looks like
/cost using Clerk for auth instead of building it myself
Money: free to 10K monthly users, then $0.02 per user. At your scale, that's $0 for roughly a year. Build time: about an hour versus 2-3 weeks doing it yourself. Lock-in is the real cost: your user records live in their system, and migrating away later is a real project. Maintenance: near zero versus owning password resets and session bugs forever. For where you are, Clerk wins. Revisit if you pass 50K users.
Illustrative exchange. Output adapts to your actual project.
When to type /cost
- You're choosing between two services and the pricing pages don't answer the real question
- You want to know when a free tier stops being free
- Someone recommended a tool and you want the catch before you wire it in
- You're deciding whether to build something yourself or pay for it
Pairs well with
Works in every major agent
/cost installs as a plain file in your project and runs wherever your agent does.
Get /cost and 21 more commands
Install it once. One license gets your agent the full Boost OS menu, seven always-on guards, and a memory of your project that survives between sessions. Lifetime updates.
From $99 · 7-day refund · license key emailed instantly