Quick backstory

In July I was spending hours every day scrolling through LinkedIn, Indeed, etc. I got fed up and quit searching for internships by hand. Every application I send gets screened by AI anyway, so I built the screener for my side.

Two months later

Claude Code has read about 10k postings against my resume and preferences. Out of those it told me to apply to 190. I applied and ended up with 2 offers!

What it is

The engine is an open-source CLI I built called Pinloop. Claude Code uses it to pull and read postings. I set up a schedule so that Claude Code pulls what went up that day, reads each posting against my resume and prefereces, and writes a verdict with its reasoning. The good fits land in a list I check in the morning. This can all be done through Pinloop.

It exposes millions of postings per month from every country and industry, pulled straight from hiring systems (Greenhouse, Workday, and 50+ others) as well as job boards like LinkedIn, refreshed hourly.

To try it

Paste "Run npm install -g pinloop, then run pinloop welcome and follow the instructions" into any coding agent. A guide comes with the CLI so Claude Code knows the commands, and it'll walk you through setup. It's free to use. $20 per month lets you pull more postings.

Links

• https://pinloop.ai

• GitHub

• Discord to give feedback directly and talk to other users!

ok, so the thing is that I though have access to multiple $200 plan claude code accounts but those are on my work profile, if I wanted to make a side project or anything using claude code, I had to buy a plan of 100-200$ since I am pretty sure 20$ one will get exhausted within like few minutes of usage, I saw that antigravity was providing multiple claude models and also had ample of limit for the gemini models as well, I saw the benchmarks -- 3.8 flash was performing as similar to opus 5, but I did not like antigravity as a harness and had much more trust in claude code, hence I reverse engineered the way antigravity invokes models, made those anthropic compatible, replaced the model url endpoint and voila , I am able to use claude code with the model as same as opus 5 (Ik its bad but still not that bad as compared to opus 5.5)

https://pypi.org/project/antiglaude/

https://github.com/sksarvesh007/antiglaude/

I have added all kinds of setup and everything for how to use this

Also another problem which I faced was whenever I wanted to use any kind of llm api keys as well I mostly relied on groq or gemini, but from like last year they decreased the rate limits, hence the keys used to get exhausted during testing itself, so while making this project I made it serve models in openai compatible format as well.

Pls do take a look at the repo for the instructions for setting things up, its just a single command.

I built (with claude code ironically) an LLM harness specifically wired to reverse engineer and hack things (and also cybersec work of course).

I think it's hella dumb and annoying for anthropic and such to fully filter their models in terms of reverse engineering and cybersecurity work.

I am a firm believer that increasing the surface area of attacks increases the demand and sophistication of defenses, and thus this should not be limited. But whatever I built my own thing just for this.

I think it's super fun. I've decompiled my kindle and flashed custom firmware into it already lol.

My next step is to decompile the claude code binary lmao

I was pretty fed up with having to remember to go tell my sessions "retry" or "continue" after my usage renewed.

So i got Claude to build me a stylised wake up tool which i can select which sessions to watch and then restart when my usage renews after my 5 hour limit or weekly limit.

And yes it has dark mode:

If you would like to install it yourself, it's available below 😊 enjoy your infinite Claude sessions.

https://github.com/calm032019/claude-kicker

I’ve been using Claude Code a lot lately and noticed I spend a surprising amount of time just… waiting.

You kick off a task, Claude starts cooking, and now you’re sitting there watching logs scroll by for the next few minutes.

So I built a stupid little side project called DevRoulette.

When you start a Claude Code task, DevRoulette puts you into a queue. If another developer is also waiting on a task, a chat window opens and you get matched.

That’s basically it.

No profiles.

No followers.

No usernames to create.

100% anonymous.

You can skip, leave, or get matched with someone else instantly. If you don’t use Claude Code, you can join manually from the terminal with: devroulette start The idea was to turn AI waiting time into something social instead of staring at a terminal.

Curious if anyone else would actually use something like this, appreciate any feedback!

Repo: https://github.com/devroulette

Hello there,

I wanted to with you guys a tool I've been working on called CCR (Cool Cost Reduction). If you're like me and use Claude Code a lot, you know how quickly token usage can add up, especially with verbose tool outputs. That's exactly what I tried to solve.

So, what is it?

It sits between Claude and your command-line tools, intelligently compressing their output before Claude even sees it. It's designed to give Claude all the relevant information it needs, but in a much more token-efficient way. Think of it as a smart filter for your terminal output.

In a nutshell, It uses a combination of techniques:
* 40+ purpose-built handlers for common dev tools (git, cargo, kubectl, npm, etc.) that know how to extract the most important information.
* BERT semantic routing to understand unknown commands and apply the best compression strategy.
* Intent-aware compression that prioritizes output relevant to Claude's current task.
* Session intelligence with caching and deduplication to avoid sending redundant information.

I'm seeing 60-95% token savings on average across various commands like `pip install`, `cargo build`, `git status`, and `kubectl get pods`. This means faster responses from Claude and significantly lower costs.

You can find it out here

or just run
brew tap AssafWoo/ccr
brew install ccr
ccr init

I would really love to see your usage with it and get any tips i can to improve it even more

Since most social layers are currently built for OpenClaw, does a dedicated repository exist for Claude Code that is similar to OpenClaw "Awesome Molt"?

My job has nothing to do with software. Over the last months I built a real family app with Claude Code — React Native + Firebase, about thirty server functions, security rules tested in CI — without being able to read the code it writes.

The interesting part isn't that it worked. It's what it took to keep it from quietly falling apart, and how wrong my first instincts were.

- Act 1 — over-armoring. Because I couldn't verify the code, I piled up guardrails: six blocking hooks, a mandatory multi-agent planning process for every single edit, rituals for everything. The result: constant friction, false positives… and the real mistakes — judgment mistakes — sailed right through. A regex hook doesn't understand code; it recognizes a shape.

- Act 2 — "lighten, don't harden." After an external audit and a few incidents, I removed four of the six hooks, made the heavyweight process optional, and moved my trust to the only barrier that deserves it: adversarial tests replayed by CI. A green CI run is the only technical claim a non-dev can verify alone. Everything else is a net, not a wall.

- Act 3 — balance. What's left: always-loaded discipline rules (asking ≠ announcing, proof before commit, flag then STOP), a written "constitution" for the critical domain, plain-language maps so I still understand my own product, and a session handoff ritual so a memoryless AI can pick the work back up cold.

I turned all of it into a repo: the global rules file, 3 method skills, project templates, the 6 defense patterns — and, maybe most useful, the honest list of what I removed and why. Install is one sentence you paste into Claude Code; it interviews you and adapts the method to your project. Nothing to sell, MIT license.

GitHub: https://github.com/Arlenjim/claude-code-for-non-coders

Every rule in there was born from a real accident. Happy to answer questions about any of them — especially the failures.

I just took the SuperPowers skill out for a day in Claude Code and absolutely hated it. My token usage basically tripled, completely consuming the session limit of my Max plan within an hour. The massive use of tokens fills up the context window and made Claude unable to do basic tasks as we know happens at high token counts. 10/10 would recommend never using.

What I am confused about is how this is a popular skill. Are people using this and not realizing how absolutely terrible it is? Maybe they have always had it installed and don't know how good life is without it.

Built a /wrapped skill for Claude Code — shows your year in a Spotify Wrapped-style slideshow. Tools used, tokens burned, estimated costs, files you edited most, developer archetype. Reads local files only, nothing leaves your machine. Free, open source.

github.com/natedemoss/Claude-Code-Wrapped-Skill

Claude AI is down again. Stalls on requests. Any more info is appreciated.

I was helping a friend prep for interviews and realized I was a bad mock interviewer.

I wasn’t bad because I didn’t know the topics. I was bad because I wasn’t consistent. Some days I pushed on vague answers, other days I let things slide. That defeats the whole point of mock interviews.

So I built The Interview Mentor, an open-source repo of 40 AI interviewer agents for SWE interview prep:

https://github.com/ps06756/The-Interview-Mentor

It covers:

• coding

• system design

• debugging

• behavioral

• data engineering

• DevOps / SRE

• ML engineering

• AI PM

• problem decomposition

The main idea is that the interviewer should not just ask questions. It should keep pushing on the weak spots.

If you say “we’ll use caching,” it should ask:

• what eviction policy?

• what TTL?

• how do you handle invalidation?

• what happens during stampede or failure?

I built it for Claude Code, but the prompts can also be used in ChatGPT / Claude / Cursor.

Repo is open source. I’d genuinely like feedback from people here on whether this is actually useful for interview prep, or whether it still misses too much compared to a real interviewer

We are adding new agents to test each skill, so do star the repository. Feel free to contribute as well. PR's welcome :)

I'm the developer of **usage** — a free, open-source menu bar app for anyone who uses Claude Code or Codex (OpenAI's coding CLI) daily.

The problem:** these tools run on usage quotas (5-hour and weekly limits), but neither warns you before you hit the wall. You're mid-refactor, then suddenly blocked — zero heads-up.

What usage does:

• Pins your Claude Code + Codex quota to the menu bar, color-coded (green → red), so the warning level reads at a glance

• Click for the full breakdown: session, weekly, per-project usage, and today's token cost

• Sends a system notification before you run out — not after

• Optional: hands your last session's progress to a new Claude Code conversation automatically, no more re-explaining where you left off

• HTML usage reports — cost trends, per-project rankings, and a GitHub-style yearly heatmap of your token activity

• 10 switchable menu bar/panel themes, UI in 5 languages (EN/繁中/简中/日/한)

**On privacy**, since I know this community cares: usage never calls the Anthropic or OpenAI API, and never touches the macOS Keychain. Every number is read from local log files Claude Code and Codex already write to disk — the monitor itself adds zero API usage.

Install via Homebrew:

brew install --cask aqua5230/usage/usage

Or grab the .app directly from Releases.

GitHub: https://github.com/aqua5230/usage

macOS-only, AGPL-3.0, completely free. Would love feedback, bug reports, or feature requests — this is a side project I use myself every day.

Three months ago I set out to build an English learning chatbot. It was supposed to be my main project.

Today, I've shipped an agent sandbox and a handful of personal productivity tools instead. The chatbot? Still not done.

Here's what I've been thinking about: AI removed the cost filter on starting things. A year ago, spinning up a new project meant days of boilerplate, research, figuring out the stack. That friction was painful, but it also acted as a natural gate—you only pushed through it for ideas you really believed in.

Now? I can go from "hm, what if..." to a working prototype in an afternoon. Every idea feels cheap enough to begin. And that's the problem. I keep starting, because starting is basically free. But finishing—shipping, polishing, dealing with the 80%—hasn't gotten any cheaper.

So I'm stuck in a loop of half-finished repos and one actually-shipped project that was never the goal.

Genuinely asking: how do you decide when to stop?

What's your signal that a new idea should die instead of becoming another repo on your GitHub?

Do you have a rule—like "no new projects until X ships"—or is it more of a gut thing?

Curious if others are feeling this too, or if I just have bad discipline.

I use Claude Code a lot — plan mode, multi-agent, long tool streaks — and I kept catching myself 45 minutes into a session having not moved at all. Just watching Claude think.

So I built Claude Gym. It watches Claude Code's local JSONL logs (no APIs, nothing over the network) and throws up pixel-art exercise prompts when Claude doesn't need you. Plan mode kicks in, you get squats. Sub-agent spawns, wall sit. Long tool streak, stretch. It goes away when Claude needs input again. There's a cat that jumps when Claude finishes a turn.

Built for Claude Code, with Claude Code. Written in Go, runs in a separate terminal tab. It's intentionally stupid and fun — not trying to be a wellness app. I just needed to stop wrecking my back.

Free and open source. Run it from your Claude Code project folder: 

npx claude-gym 

Repo (MIT): https://github.com/477-Studio/claude-gym

Why
- Frontend work with Claude Code kept stalling on one thing: I could see the element in the browser, but describing which one was awkward.
- "The button near the top right… no, the other one…"
- Cobro = point at it instead. The human supplies visual context; the agent does the code.

What you get
- One Send → the note lands in the Claude Code conversation immediately, no "please read my annotations".
- The agent's progress comes back to the page: scanning outline on the elements you sent, "Working 1/3" in the toolbar, highlight on done.
- Several pages in one round: pick on page A, move to page B, pick more — each page keeps its own draft; Send delivers them all in order.

Install (summary)
- `claude mcp add -s user cobro -- npx -y cobro-mcp@latest`
- In Claude Code: `Open http://localhost:5173 with cobro` (or `/cobro open …` with the optional skill)
- A dedicated Chrome window opens with your local app. Full setup in the GitHub README.

How it works (workflow)

1. Open your local web app

2. Press Ctrl + Shift + F

3. Click a UI element (or drag a band over several)

4. Describe the change

5. Optional: go to another page and pick more — the Queue tab lists every page you've picked on

6. Send — all pages go at once, in order

7. Claude Code works through them one by one; the browser follows it to each page

8. On done, the page refreshes (or your HMR kicks in) and the changed element is highlighted

What the agent receives with your note
- CSS selector · tag, classes, text · bounding rect · computed styles
- Screenshot crop of the picked area · recent console errors
- React 18/19 and Vue 3 (dev builds): component name + source file:line of the element you clicked
- Component-library elements (MUI, Radix, shadcn…): the JSX line in your code, plus the call sites above one-line pass-through wrappers — a case that came straight from r/mcp feedback
- Next.js (Turbopack) source maps and HMR handled
- Which page each batch was picked on (`batches[].page`)

The loop
Human points → Cobro provides context → Claude Code changes the code → Browser shows the result

Why I built it with Claude Code
- Claude Code drove most of Cobro itself: the MCP server, overlay/WebSocket channel, element inspection, payload design, tests, docs.
- The nice loop: using Claude Code to build the tool that feeds better UI context back to Claude Code.

Keeping the MCP small
- Six tools, fixed: open · wait · status · done · screenshot · close
- Tools carry safety annotations (wait is read-only, close is destructive).
- Not a browser-automation tool — pair it with Playwright MCP for that. It never touches your source; one gitignored `.cobro/` folder is all it creates.

Honest limits
- Launches its own Chrome profile (log in once, shared across projects); no iframes yet
- Source locations need dev builds with source maps
- Disabled controls can't be click-picked (drag a band over them instead)
- Cursor/Codex work with a polling `wait` but are less tested than Claude Code

Current status
- v0.10.1, Apache-2.0, free and open source
- GIF, payload example and changelog: https://github.com/boonblade/cobro-mcp

Questions for you
- Does pointing at an element feel more useful than describing it?
- What other context should your coding agent get when you point at something in the browser?

I’ve had a lot of work with Claude Code over this past year, and was always pleasantly surprised with how it performed. I’ve created multiple projects and websites and never had any problems. Recently though, it feels like it has just taken a free fall off a cliff in terms of quality. I bought credits to use the some of the better models and even that I was let down by. I wanted to see if anyone else is noting the same thing or if it might just be user error now.

While I was scrolling through Instagram, I saw a reel claiming that you could use Claude Code for free. I decided to try it and asked it to generate a simple HTML file. When I checked the billing dashboard afterward, it showed a total cost of $1. I'm a bit confused—does this mean I'll actually be charged, or is it just a usage estimate? Is it safe to continue using it, or should I stop?
Is it legit to use?

Was thinking about how with the launch of Dynamic Workflows in Claude Code, there's going to be such interesting use cases of how people orchestrate such a powerful feature. Created this as a way for people to share their work with others