First-party only — a session id and where you arrived from, so we can tell which pages are worth writing more of. No advertising, no third-party trackers, nothing that follows you off this site.
Everything that goes in the repo before you type a single prompt.
Most bad agent output is not a prompting problem. It is a configuration problem — the agent never had the context, the boundaries, or the commands it needed. This pack is the setup layer: memory files, skills, slash commands, hooks and permission policy, written to drop into a real repository.
One-time. Yours permanently, including every future update.
You’ll enter your email first — a purchase has to be attached to an account so it does not get lost. It takes about fifteen seconds and brings you straight back here.
Nothing is hidden until after you pay. This is the complete contents. Files marked readable can be opened in full right now, without an account.
Read this first — the install order matters more than the contents.
What is in the pack and the order to install it.
The single highest-leverage thirty minutes. Four repo shapes, plus the reasoning so you can adapt rather than copy.
The inclusion test, the five things worth including, what to leave out, and how to keep it true.
A single deployable service with a database. Commands, invariants, gates, prohibitions.
Multiple apps and shared packages. Dependency rules and package-scoped iteration.
A package other people depend on. The public API as a contract.
Confidence markers for the situation where you do not know the invariants either.
The vendor-neutral packaging, for when you use more than one tool.
Procedures the agent loads only when the work matches. Add one after the third time you have explained it.
Format, porting table, and when a skill is the wrong tool.
Expand/contract, lock analysis, batched backfills, and the four questions to answer first.
The contract questions to settle before writing, and the failure cases agents skip.
Adding, upgrading, removing. Lockfile discipline and advisory triage.
Restore first, diagnose second. The rules that change during an incident.
Failure-rate diagnosis, the five causes, and why reproduction has to come first.
Refuse to optimise before measuring. Where to look by symptom.
Prompts you invoke by name. Start with /repro and /handoff — those two pay immediately.
Format, porting, and what makes a command worth creating.
Reproduce with a failing test before proposing any cause.
Draft a memory file for a repo you have just been handed.
Turn a vague request into a spec, adversarially.
Four review passes, expensive problems first.
Summarise a session so a fresh one continues without the debris.
Pre-merge checklist that verifies rather than asserts.
Instructions are advice; hooks are enforcement. Three scripts plus the settings that wire them up.
Events, blocking exit codes, install, and how to test one before trusting it.
Wires all three hooks to the right tool events.
Refuses hand edits to generated, vendored and lockfile paths.
Refuses any write containing something shaped like a credential.
Formats each file the moment it is written, so every diff is canonical.
A policy that is safe without being annoying — sorted by blast radius, not by how dangerous a command sounds.
Allow always, allow with a boundary, always ask — and where sandboxes do not help.
The full allow / ask / deny policy, ready to merge.
What is in the pack and the order to install it. This is the actual file, not an excerpt.
# The Agent Operating Kit
Everything that goes in the repository *before* you type a prompt.
Most bad agent output is not a prompting problem. It is a configuration
problem: the agent never had the context, the boundaries, or the commands
it needed. This pack is the setup layer.
## What's in here
memory/ CLAUDE.md and AGENTS.md templates for four repo shapes
skills/ Reusable skill definitions for recurring work
commands/ Slash commands for the moves you repeat every day
hooks/ Hook scripts + the settings that wire them up
permissions/ A permission policy that is safe without being annoying
## How to use it
Do not install all of it at once. In order:
1. **memory/** — pick the template closest to your repo, fill it in, commit it.
This alone is most of the value. Give it thirty minutes.
2. **permissions/** — copy the settings file, adjust the allow list to your
build commands. Ten minutes.
3. **hooks/** — add the two you will actually notice: format-on-write and
secret-scan. Skip the rest until something annoys you.
4. **skills/** — add one when you have done the same kind of task three times.
Adding them speculatively wastes context.
5. **commands/** — same rule. Start with `/repro` and `/handoff`.
## Which tool is this for
The memory templates work with anything that reads a project instruction
file: Claude Code (`CLAUDE.md`), Codex and friends (`AGENTS.md`), Cursor
(`.cursor/rules/`), Windsurf, Cline, Roo Code.
Skills, commands and hooks use Claude Code's format because it is the most
expressive. `skills/README.md` explains how to port them.
## Licence
Yours to use in any project, personal or commercial, including your
employer's private repositories. Do not resell or republish the files
themselves.
Version and changelog: see the pack page on pairfoundry.com.14-day refund, no explanation needed. If it does not earn its price, say so and we send the money back.