I Built a Weekly Directory for Claude Code Agents (Because My Brain Couldn't Keep Up)

A few weeks ago I wrote about hiring 131 AI employees by installing a big pre-made subagent pack. That post still holds up. But since then, something annoying has been happening.

Every single week, I open X, or GitHub, or some random Discord, and trip over another Claude Code agent I'd probably use if I remembered it existed. A new code reviewer. A smarter debugger. A security auditor that actually explains things. People keep shipping these, and I keep forgetting them by Tuesday.

The problem isn't a lack of tools. It's that the good ones get buried under the average ones, and nobody has time to sort through it every week. Especially me — I have meetings, a day job, and three kids of small side projects that already demand attention.

So I did what any reasonable vibe coder would do: I built the thing I wished existed instead of remembering to check a bookmark folder.

It's live at agents.vibed-lab.com.

What Is This, Exactly?

It's a directory. That's 80% of the pitch. But it's a directory with two specific habits that make it different from "just browse GitHub":

┌────────────────────────────────────────────────┐
│  agents.vibed-lab.com                          │
│                                                │
│  ┌───────────────┐   ┌───────────────┐         │
│  │ THIS WEEK'S   │   │ TRENDING      │         │
│  │ FEATURED      │   │ (auto)        │         │
│  │               │   │               │         │
│  │ hand-picked   │   │ sorted by     │         │
│  │ by me, with   │   │ weekly star   │         │
│  │ a one-line    │   │ growth        │         │
│  │ note          │   │               │         │
│  └───────────────┘   └───────────────┘         │
│                                                │
│  ┌────────────────────────────────────────┐    │
│  │  CATEGORIES                            │    │
│  │  review · testing · debugging · ...    │    │
│  └────────────────────────────────────────┘    │
└────────────────────────────────────────────────┘

Two surfaces:

• Featured — a small number of agents I personally picked this week, with a one-liner explaining why I'd bother installing them.
• Trending — the rest of the ecosystem, auto-sorted by how many stars each repo gained in the last 7 days. No opinion, just momentum.

You come once. You see what's worth a second look. You leave. Next Monday there's new stuff.

The Weird Part: There's No Backend

I almost always regret building side projects that need a database. Something breaks at 2am, a free tier expires, a password rotates, I give up. So this one has no backend at all.

Here's how it updates itself:

  ┌──────────────────┐
  │ Monday 00:00 UTC │   ← GitHub Actions cron
  └────────┬─────────┘
           │
           ▼
  ┌──────────────────┐
  │ Crawl GitHub     │   ← searches for claude-code-agent topic,
  │ for agent repos  │     claude-code-subagent topic, etc.
  └────────┬─────────┘
           │
           ▼
  ┌──────────────────┐
  │ Filter spam      │   ← < 5 stars → drop
  │                  │   ← dead 1+ year → drop
  └────────┬─────────┘
           │
           ▼
  ┌──────────────────┐
  │ Compare vs last  │   ← compute 7-day star delta
  │ week's snapshot  │     = "trending" ranking
  └────────┬─────────┘
           │
           ▼
  ┌──────────────────┐
  │ Write JSON file  │   ← data/agents.json
  │ and git commit   │
  └────────┬─────────┘
           │
           ▼
  ┌──────────────────┐
  │ Cloudflare Pages │   ← auto-rebuilds the static site
  │ redeploys        │     on every push
  └──────────────────┘

That's the whole machine. A cron job commits a JSON file. Next.js reads the JSON at build time and renders every page into plain HTML. No database. No server I have to keep alive. No rate-limited API the site depends on at runtime. Total monthly cost: $0.

The first crawl pulled in 216 agents. On day one.

Key detail: The site will keep working even if I get hit by a bus. The JSON just stops updating. Everything that's already there remains browsable. That's the point of static sites — they're basically a printed pamphlet that happens to be on the internet.

What Can You Actually Get Out of This?

Three things, in order of how lazy you're allowed to be:

Lazy mode. Open agents.vibed-lab.com on Monday morning with coffee. Scroll the Featured section. If something looks useful, click it, copy the install snippet, done. Total time: 90 seconds.

Medium mode. Pick a category (Testing, Debugging, DevOps, etc). Scroll the trending repos in that slice. See what the ecosystem is pushing toward this month. This is how you notice a pattern — like "oh, three new security auditors shipped this week, that must be a moment."

Gremlin mode. Watch the trending list week over week. Star-delta is a better signal than total stars for "what's hot right now." Old repos with 5,000 stars that haven't moved in 6 months sink. A 40-star repo that gained 30 stars this week floats to the top. That's where the interesting stuff hides.

How to Prompt AI (About Using This)

If you use Claude Code and want it to help you browse smarter, try something like this:

I'm on agents.vibed-lab.com looking for a Claude Code subagent for [X specific task]. I'll paste the README excerpts of the top 3 candidates. Compare them for me: which one is actually best at the task, which one is marketing fluff, and which one is already covered by a built-in tool I don't need to install?

That last part — "already covered by a built-in tool" — is the one people always forget. Half of new agents reinvent something that already exists. Claude is good at telling you when you're about to install a duplicate.

Tip: If an agent's README is mostly screenshots and zero examples of actual prompts or outputs, it's usually a vibe and not a tool. Skip it.

Why I'm Doing This (And Will Keep Doing It)

Honestly? Selfish reasons.

I was going to look at new Claude Code agents every week anyway. Once I realized that was inevitable, I figured I might as well turn my weekly 20-minute search into something other people could benefit from. The incremental cost of a public directory vs. a private bookmark folder is basically zero — and one of them lets me stop feeling bad about not sharing.

Also, I trust hand-picks more than I trust "1.2k stars." Stars are lagging. A repo can go viral, collect stars, and be abandoned — the stars don't move. What I wanted was a human who uses this stuff saying, "yep, I'd install this one today." That's the Featured section. The trending list handles the firehose; the Featured section handles the signal.

Quick Reference: When to Check What

If you use Claude Code, bookmark agents.vibed-lab.com. It'll get better every Monday whether I show up or not. That's the magic of accidentally shipping a machine that doesn't need me — I didn't set out to run a hardware store for people who also don't own power drills, but here we are.

2026.04.11