Latest release
AgentWrangler
A local, privacy-preserving observability tool for Claude Code token spend and session outcomes. A daemon on 127.0.0.1 streams your ~/.claude transcripts into SQLite and surfaces cost trends, hygiene findings, and GitHub outcome linkage — so you can measure and cut agent waste without any data leaving your machine. Shipping soon; the two token-economics field notes below are the teaser.
The register
Every project gets a verdict and a line on what carried forward. The scrapped ones count as much as the launches. Click any row for the full case study, or cross-read the security controls →
The timeline
Jan 27 – Aug 25, 2026. Bar length is calendar time; the labels are commits. Overlaps are real — some of these ran in parallel across ~35 agent worktrees.
The build journal
The same 136 days as a sequence of decisions. Dates marked ~ are approximate.
RiskScanAI begins — before the repo
The first build starts off GitHub: landing pages and product shaping ahead of any version control.
RiskScanAI — first commit lands on GitHub
First product, first AI-agent workflow. 160 commits over the next 15 active days.
PreCloseIntel — full PRD, then a pausePAUSED
First run of the 7-phase Idea → Build framework. The PRD survived; the build slot went elsewhere.
RiskScanAI shelved — and forked the same daySHELVED
The honest read: nobody pays for an AI-interview risk assessment. Everything carried directly into CyberReadyAI on the day of the last commit.
PartMatch scrapped at PRD reviewSCRAPPED
Adversarial review said “spike first.” Stopping it cost a review session instead of a build month.
TariffRefunded beginsLIVE
The tariff rate monitor PRD dies; refund recovery for SMB importers replaces it, racing a 180-day protest window.
CyberReadyAI paused with intentPAUSED
Near-launch after 747 commits. The project that taught me to audit my own guardrails.
SafeCircleOps — a five-day sprint for a friendPRIVATE
140 commits in 5 days. Local-only, evidence-grade, deliberately unpublished. Report delivered to law enforcement.
DealFinder — a seven-day MVP, then a pausePAUSED
Ideated inside the SafeCircleOps build, three days in. 130 commits to a working real-estate intelligence MVP, then paused unlaunched.
ReadySetBind — first commitLIVE · PILOT
813 commits and 243 PRs in the first 17 days. Day one shipped the end of the pipeline before most of the middle existed.
StackBadger publishedPUBLISHED
A pentest harness extracted from TariffRefunded, scrubbed, and released. The extract → scrub → review playbook becomes repeatable.
ReadySetBind live in pilot — and this register goes up
Eight products, two live, one published, one report delivered. The scrapped ones count as much as the launches.
Pipeline-Hygiene publishedPUBLISHED
A read-only sales-pipeline inspection agent: eleven deterministic hygiene rules flag stale, slipped, and mis-forecast deals before the forecast call, each flag tracing to a versioned threshold. Agents inspect, people sell. 137 commits · 37 PRs across 4 active days.
GridSignals publishedPUBLISHED
Turns the public record around 172 US energy companies into scored, sourced signal cards, mapping regulatory and incident events to Microsoft security products. Stdlib-only pipeline, 84-module test suite, honest empty states. 337 commits · 115 PRs in 9 days.
Seller-Admin-Tools publishedPUBLISHED
An offline, deterministic toolkit that turns a weekly CRM export into the forecast narratives, QBR decks, and account plans a seller builds by hand — adapted from an enterprise security-sales methodology. On-screen numbers and the exported decks cannot disagree. 72 commits · 10 PRs in 3 days.
SecuritySalesHub — a multi-vendor restack beginsIN PROGRESS
GridSignals, generalized: pre-sales signal intelligence across energy, financial services, and healthcare, recommending security products from 47 vendors instead of one. A two-hop event → capability → product path keeps every suggestion auditable. Still building; deploy not yet wired.
Latest posts
Field notes from building with AI agents — specific incidents, real numbers, no generic advice.
Where your Claude API bill comes from
The subscription version of this cut me off for a week. The pay-as-you-go version doesn't cut you off — it just bills you, and everyone blames the same wrong thing. Your invoice is fully explainable from four numbers on every response.
Why you hit your Claude Code limit
I hit the Claude Max weekly cap two weeks running and blamed my CLAUDE.md. It was the wrong suspect. The real drain is a cache miss — invisible on any per-token chart — and the fix is a habit, not a diet.
A human watching AI isn't oversight
An AI agent told me the emails had all sent. Some never left the building. The return code said success; reality didn't. That gap is the whole problem with 'keep a human in the loop.'
The graveyard
Ideas that got a real PRD, real research, or real validation — and a deliberate no. Each one has a reason on record.