realgenekim

Switching an autonomous SBEK evaluation fleet from Claude Opus to Codex CLI

Credit where it is due

This work builds on Mike Lay’s amazing SessionBoard Eval Kit (sbek).

SBEK does the hard and important work: it defines the evaluation scenarios and rubrics, drives a browser through MCP, records evidence, separates browsing from fresh-context judging, validates judgements, and produces the final score. It is thoughtfully designed, unusually rigorous, and was a joy to build on.

The adapter described here does not replace SBEK and should not be mistaken for its original implementation. SBEK already documents a harness path for both Claude Code and Codex. Our narrower contribution is automating that path as an unattended fleet: one fresh codex exec process per worker and judge, selected behind a rollback-safe executor flag.

iannuttall

AgentOS — Product Spec & Implementation Blueprint

Reconstructed from Danny Postma's talk How I Built My Own AgentOS on Claude's Agent SDK (So You Can Too) (2026). This document is both a product spec for a human and an implementation prompt for an AI coding agent. Build exactly this system. Do not invent features that are not specified here.

Role contracts and prompts in this file are reconstructed from the talk, not his verbatim files. Mark every reconstructed prompt in code comments and docs as such.

---

1. Goal and non-goals

pizlonator

This document explains how I would implement an SSA-based compiler if I was writing one today.

This document is intentionally opinionated. It just tells you how I would do it. This document is intended for anyone who has read about SSA and understands the concept, but is confused about how exactly to put it into practice. If you're that person, then I'm here to show you a way to do it that works well for me. If you're looking for a review of other ways to do it, I recommend this post.

My approach works well when implementing the compiler in any language that easily permits cyclic mutable data structures. I know from experience that it'll work great in C++, C#, or Java. The memory management of this approach is simple (and I'll explain it), so you won't have to stress about use after frees.

I like my approach because it leads to an ergonomic API by minimizing the amount of special cases you have to worry about. Most of the compiler is analyses and transformations ov

aarondfrancis

Audit this entire codebase for materially useful simplifications in its data structures, state representation, control flow, algorithms, and ownership.

This is an audit-only exercise. Do not edit files, run tests, implement recommendations, commit, or push. Read-only inspection commands are allowed.

You are the coordinator. Continue until the complete codebase has been reviewed and the final audit is validated.

1. Establish the coverage contract

Inspect the repository and inventory every identifiable subsystem.

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

connerdassen

apt-get update
apt-get install tmux
apt-get install git
apt-get install golang
echo "export GOPATH=/data/data/com.termux/files/usr" > and_kh_tmp1
chmod +x and_kh_tmp1
sleep 1
source and_kh_tmp1
echo "Downloading kahoot-hack... Please wait"
go get github.com/unixpickle/kahoot-hack

mcollina

Configuring minimum release age across npm, pnpm, and yarn

Setting a minimum release age (a "cooldown") on dependencies is a cheap, high-leverage defense against supply-chain attacks. Most malicious package versions are detected and yanked within hours, so a 24-hour delay filters out the smash-and-grab incidents (axios 1.14.1, ua-parser-js, Solana web3.js, etc.).

All three major Node.js package managers now support this, but each one used a different name and a different unit. Here is what you need.

Minimum versions

Tool	Setting	Unit	Introduced in