One line at the bottom of Claude Code: how much of the context window is gone, how much of the weekly budget is spent, and which model is answering. Every figure is read from the payload the harness pipes to the script on stdin, so nothing is host-specific. Needs node and nothing else.
2 skills
A handbook you hand to your agent: material for the general judgement calls — architecture decisions, planning, the rules that hold whatever is being built. Nothing here is tied to a language, a stack or a framework, and nothing installs a runtime, calls a network or needs hardware. It holds two kinds of thing: an instrument you reach for at a moment — `/target-world-walk`, which derives what a plan needs by replaying one concrete unit of work through the system you intend to have — and two standing rules that are never invoked at all — the flagellant rule (which reports a mistake as fact plus fix rather than apology, stops when the stopping condition is met instead of re-checking finished work, spends care where an error cannot be taken back, and reports completion only by first naming what would still be outstanding if it were wrong) and the non-stop rule (which says: do the work and report it rather than asking permission, write in the past tense, never hand back the turn while work remains, ask a question only where the work becomes pointless or unsafe without the answer, probe your own rights with a command before saying a task needs a human, report done only with proof, and never write farewell summaries). Both standing rules arrive through a SessionStart hook, so they compose with whatever output style you have chosen rather than replacing it.
1 skill
Shared core for windowsill plugins: assistant state store with atomic writes, remind-once etiquette, and schema-versioned JSON persistence. One file per plugin in the user's state directory.