Boring Layer

We make configuration, deterministic guardrails and documentation for agentic coding tools. The unglamorous parts you rebuild on every repo and nobody sells.

Two ideas run through everything here. Guarantees belong in hooks, not in instruction files, because a rule a model can decline to follow is a suggestion. And a config is not finished when it reads correctly, only when it has been run: we shipped a security hook that exited 0 and protected nothing, and the only reason we caught it was a test that had to fail.

What we make

Agent Ops Kit

Sub-agent definitions, hooks, slash commands and CLAUDE.md starters you drop into a repo and use the same hour. One-time purchase. Nothing to host, no account, no subscription.

Agent Ops Starter

Three sub-agents, a secret-scan pre-commit hook and a cost cheatsheet. MIT, free, no signup, short enough to read before you run it.

How we write

• Every claim traces to an executed test or an existing file. If we cannot back it, we delete it rather than soften it.
• We publish the failures. The bugs we found in our own configs are in the documentation, because they are the part worth reading.
• Counts are exact. Eight sub-agents means eight.

About this page

This page has no stylesheet. Not a minimal one. None. What you are looking at is the browser's default rendering of ordinary HTML, which has been a solved problem since roughly 1996.

It loads instantly on any connection, reflows correctly at any width, inverts properly in dark mode without being told how, stays readable with images and scripts disabled, and works in a text browser and a screen reader. There is no build step, no framework, no font to download, and nothing on it that can break. It will never need a redesign.

We sell the boring layer. It would be strange to arrive dressed otherwise.

Contact