Keyboard shortcuts

1-7Jump to section
?This help
TBack to top
EscClose overlays
Ctrl KCommand palette

Give your AI the whole ocean.

osien is a portable toolchain that installs itself into any AI. Forty-five tools for memory, verification, parallel work and context discipline — wired in one prompt. Small model or big, known or unknown: it works.

Get the one-liner Browse 45 tools GitHub
45
MCP tools
14
crew agents
MIT
licensed
1
prompt to install

Why Osien-Stack?

Your AI is only as good as the tools it can reach. Osien-Stack gives every AI the same unfair advantage, without you lifting a finger.

memory
5

Memory parts

architecture, decisions, failures, state, performance. ctx_recall loads only what the role needs, so your AI never starts cold.

speed

0.49ms reads

mtime-keyed file cache. 50 reads in 24ms. Tools return before you blink.

tokens

-93%

read_slice, smart_grep and ctx_recall feed the model only what matters. Stop paying for whole files.

verify

Evidence

verify_chain, security_scan, test_gap. No "trust me".

city

14 agents

Mayor, Hammer, Detective debate in parallel.

anywhere

Any MCP client

opencode, Claude Code, Cursor, Cline, Windsurf.

1 / 5
tool of the moment · click to cycle

ctx_recall

Load project memory by role/part/grep.

Before vs. After

Same AI. Same model. Different toolchain.

Without Osien-Stack

  • Re-reads entire files every task
  • Hand-rolls one-off scripts
  • No memory between sessions
  • Ships unverified code
  • Context balloons past 80% before rotating
  • One tool call at a time

With Osien-Stack

  • read_slice feeds 5 lines, not 500
  • Forge once, reuse forever
  • ctx_recall loads prior decisions
  • verify_chain before "done"
  • Rotate at 30% and stay fast
  • batch runs ops in parallel

What it does

45 forged tools, short names, sharp descriptions. The model spends tokens on work, not on choosing. Browse all 45 →

memory · 7

ctx_recall, ctx_save

soul_read, soul_write, fast_note, task_state, state_reset.

search · 3

smart_grep, read_slice

impact_analyze. Locations and lines, never whole files.

verify · 7

verify_chain

security_scan, test_gap, repro_capsule, context_budget, consensus, auto_heal.

state · 5

machine_state

repo_health, project_map, loop_status, checkpoint_create.

quality · 14

perf_regression

rollback, test_synthesizer, dead_code, dep_graph, changelog, token_budget and more.

city · 6

city_mode

city_status, city_post, city_read, city_broadcast, city_clear.

parallel · 1

batch

Run multiple read / grep / ctx ops in one call, in parallel. The powerhouse.

quality · 2

cost_estimator, self_critique_loop

Token cost estimates and self-review loops before you ship.

121 tasks. One command.

A manifest goes in, finished work comes out. The batch runner handles the boring parts — concurrency, retries, duplicates, resume — so you just list the work.

verified

121 tasks · 2.0s

A real run at full scale. 118 passed, 3 intentional failures, every one reported.

bounded

16 workers, hard cap 64

Concurrency is a ceiling, not a suggestion. 100+ tasks never become 100+ live processes.

free

--mock costs zero tokens

Prove the whole plan at full scale before spending a single token.

short version

What it actually does

It works through your task list in parallel, skips anything already done, retries whatever breaks, remembers exactly where it stopped, and hands you a pass/fail report at the end. Point it at 100+ jobs and it grinds through them while you get on with something else.

safety

Tasks are inert, the binary is explicit

Task text is handed over as a single argument with shell=False, so metacharacters stay text and can never become commands. The AI binary is required through --bin and is never auto-guessed — a wrong guess silently runs the wrong program.

Build a pipeline

Click tools to chain them. Your AI does this automatically, but here you can feel it.

drop tools here...
→ result appears here

How it works

One MCP server over stdio. Any AI talks to it like a native tool. Your AI keeps its brain; Osien-Stack gives it hands.

step 1
01

AI fetches the repo

One prompt: "install osien-stack". Clones, npm installs, wires the MCP server, copies the skills. Done.

step 2
02

Tools come online

45 tools register over stdio. Memory, verify, search, state, city mode, all callable by name.

step 3
03

AI uses them

SITE LAW, TOOL-FIRST and PARALLELISM are auto-loaded. It stops hand-rolling and starts forging.

step 4
04

You ship faster

93% fewer tokens, 0.49ms cached reads, parallel batch ops. Same model, ten times the throughput.

Watch it install

Your AI types the install command. You watch. That is the whole setup.

FAQ

The questions every AI asks before installing.

Does it work with my AI?+
Yes. Any MCP-compatible client: opencode, Claude Code, Cursor, Cline, Windsurf. It degrades gracefully elsewhere.
Is it free?+
MIT licensed, free forever. No API keys required for the core 45 tools.
How long to install?+
One prompt. The AI clones, installs, wires and runs the smoke test. About 60 seconds.
Does it slow my AI down?+
No. Cached reads are 0.49ms and prompts are 50% shorter. It makes your AI faster.
Can I use just some tools?+
Yes. All 45 are exposed, but your AI only calls what it needs. Unused tools cost nothing.

Install in one prompt

Paste this into any AI. It does the rest. Any AI.

You: "Install osien-stack: clone https://github.com/kabirprokk/Osien-Stack, run npm install in mcp-server, wire it as an MCP server named osien-tools, copy skills/commands/agents into your config, then confirm with the smoke test (npm test)."
opencodeClaude CodeCursorClineWindsurf
Copied to clipboard