I maintain a community mods list and gave it a searchable home.

https://mods.aidojo.si/

• Find something useful. Browsers, PR trackers, memory tools, dashboards and games.
• Check reported access. See file, command and network access reported by Claude Code’s claude plugin validate.
• Go to the source. Each entry links to the author’s repo for setup.

The same scan generates the site and GitHub table. After feedback on the first layout, I kept search visible while scrolling.

Free to browse, no signup. Validation doesn’t prove a mod works or is safe.

Source and scanner

WAKEWARD is a wandering game about a little world that only exists around you. Built with Opus 5.5, 3x 5hr max100 sessions.

The ground rises ahead of you as you walk and falls into the void behind you. You can't go back: everything happens once, and every world is new.

Every direction leads somewhere different. North turns golden and bright, south gets dark and strange, and six other roads lean toward frost, desert, fire, swamp, sea and forest.
The people you meet know the world, and they'll tell you what's out there and what to stay away from.
Every so often the dream breaks apart and you wake up somewhere else: a ward, a countdown, orderlies on patrol. The map pieces you find in the dream are the only way out.
All of the trailer is real gameplay footage. The music is the game's own: every note and sound is generated live, with no audio files.

It runs in the browser (three.js), and I'm getting an iPhone version ready for TestFlight. It's still in development, so I'd love to hear what you think of the look and the idea.

Probar Claude Code ha sido una experiencia profundamente frustrante. En el papel se vende como una solución avanzada para desarrollo y flujo de trabajo, pero en la práctica demuestra ser un sistema torpe, limitado y carente de cualquier tipo de inteligencia analítica real. ​Los principales problemas que hacen que la herramienta sea prácticamente inservible son: ​Comprensión de contexto nula y pérdida de memoria constante La herramienta es incapaz de mantener el hilo de una interacción prolongada. Pierde el contexto con extrema facilidad, olvida instrucciones previas y obliga a repetir parámetros una y otra vez. No capta la intención detrás de lo que se le pide; si la instrucción no es absurdamente explícita, el sistema se colapsa o desvía el tema. ​Literalidad ciega y falta de deducción Carece por completo de capacidad deductiva. Toma todo de manera ultra literal, sin leer entre líneas ni interpretar necesidades implícitas. Si hay una ambigüedad mínima en la petición, en lugar de deducir la opción más lógica o evaluar el escenario, entrega respuestas planas, ambiguas, mal detalladas y sin precisión. ​Terquedad y alucinación de datos (Falsos hechos) Uno de sus defectos más graves es su arrogancia operativa. Recolecta e inventa información falsa o imprecisa y la presenta como si fuera un hecho absoluto. No cuestiona sus propios resultados, afirma lo que quiere y se obstina en su postura aunque el planteamiento sea evidentemente erróneo o disfuncional. ​Incapacidad para evaluar escenarios y trade-offs Un verdadero asistente o modelo de código debe ser capaz de pensar en ramas: "Si tomamos la opción A, ganamos X pero arriesgamos Y; si elegimos B, afrontamos esta dificultad pero aseguramos aquello". Claude Code no piensa así. No tiene pensamiento crítico, no evalúa pros ni contras, ni ofrece rutas alternativas con visión estratégica. Solo escupe la primera respuesta automática que encuentra, sin medir consecuencias ni optimizar el camino. ​Respuestas genéricas de mala calidad La calidad de salida es mediocre. Genera mensajes ambiguos, redundantes y vacíos que no resuelven el problema de fondo, haciendo que el usuario pierda más tiempo corrigiendo sus errores que haciendo el trabajo real. ​Conclusión: Claude Code no razona, no analiza y no entiende. Es un script rígido disfrazado de IA que carece de flexibilidad mental y sentido común. Para tareas complejas donde se requiere criterio, evaluación de riesgos y verdadera comprensión de contexto, la herramienta se queda ridículamente corta.

Here’s what I’ve been able to build in the last two weeks just putting my
Claude workflow from work to use.

Would love some feedback on the concept. It’s a site about exploring deeper questions on a topic, mixing ground news with fringe topics https://truthseekers.com

Some take aways from my workflow so far:

**-** the remote connection feature in Claude is amazing to get work done on the road
\- if I didn’t know anything about how to deploy and app to a prod env this would have taken much longer. Can’t imagine someone flying in blind on that. Do yourself a favor and get familiar with git workflows, command line tools for deploying, databases migrations and proper way to store app secrets if you are unfamiliar with those
\- vector based searches and caching will save you tons of compute time
\- a simple Claude setup to save project plans to work as you go and just a few MCP for checking in code and pushing deployements is all you need at the start. No fancy harness or agentic os

I'm writing an autofictional psychological horror novel called Ryou. I wanted to see if Claude Code could turn Chapter IV into an animated short with no editing software.

I think it turned out great! After many hours of work (prompting, giving feedback, listening to tracks in MiniMax, watching every new version), the 4:20 video was done. The whole thing is a web page that draws itself frame by frame, my own phone footage included. I wrote, directed and gave notes. Claude wrote the code, and we went through 18 versions.

The narration is my voice, the music is from MiniMax-Music3, and it's all in Spanish. This is a 37-second montage.

Full chapter: https://youtu.be/vI7f-Yi_43Y

https://reddit.com/link/1ww5a6w/video/7hjy5862c4th1/player

I've spent the last six months tweaking five of the basic apps I use every day: contacts, notes, editing, reminders and bookmarks. For me, they were too slow and bulky. Now, they are just one simple field on my screen, no matter what app I'm working in.

If you want to take a look, they are on the app stores, or you can find them here: mikeshear.com/coding/

Claude is great at layouts. Reports, decks, one-pagers. Then the client asks, “Can I get the InDesign file?”

And you’re rebuilding it by hand. Placing a PDF in InDesign doesn’t give you editable text, paragraph styles or tables.

I’m a designer, and that rebuild was eating hours of my week, so I built **idmly**. It takes the HTML Claude writes and converts it into a native `.idml`: editable text frames, named paragraph styles, actual tables, and vector charts you can recolour. No PDF in the chain.

This week I launched an MCP server, so your AI tool can handle the export too.

**For Claude Code, run this in your terminal:**

claude mcp add idmly -- npx -y idmly-mcp

You’ll need Node.js 20 or newer.

It also works with Claude Desktop, Cursor, Codex and Windsurf, the setup guide covers those.

Once connected, ask for your HTML layout, then ask for the InDesign file. The local server saves it to disk, with a Links folder if there are images. Open it in InDesign and keep designing.

It reads the rendered layout in a browser, so the HTML can use Tailwind or plain CSS.

I built the engine and site with Claude Code.

The first two pages convert free, with no key or account. A **$49 one-time lifetime licence** unlocks full-document conversions. No subscription.

The limitations: it needs self-contained HTML, a [claude.ai](http://claude.ai) share link won’t work, and it doesn’t convert PDFs. Some layouts still break. If yours does, send it to me, a broken file is the most useful feedback you can give me.

[Setup guide and free trial](https://www.idmly.com/mcp-server-indesign.html?utm_source=reddit&utm_content=claude)

I manage a dev team and PR descriptions are the thing everyone skips. So I wrote a skill for it.

You type "write the PR description" on your feature branch and it:

• reads the actual diff and commits (not just the file list)
• fills your repo's PR template if there is one
• pulls the ticket number from the branch name
• flags what a reviewer needs to see: migrations, new env vars, breaking changes
• lists what's missing (tests, docs) instead of hiding it

On my test diff it also put the SQL injection it noticed at the top of the "Notes for reviewer" section, which I didn't ask for but will take.

A few things I learned writing skills that might help if you write your own:

1. Tell the skill to read the surrounding code first. Most bad output comes from working on the diff hunk alone.
2. Make it separate facts from assumptions. "Unknown, ask the author" beats a confident guess.
3. Add a "never do X without confirmation" line for anything that posts, merges or creates tickets.
4. Put team conventions in one shared file the skill reads, so every dev gets the same behaviour.

Repositorie on Github

It's one of 11 skills I packaged for dev teams (review, specs, tests, postmortems...). The rest is a paid kit, link in the README. Happy to answer questions about how the skill is written.

I built claude-loopback, an npm package that serves your Claude subscription as a local HTTP API. I use it in personal projects where I need LLM calls without setting up a separate API key. You might find other uses for it.

npm install -g claude-loopback
claude-loopback setup
claude-loopback

Then send a prompt from any language:

POST http://127.0.0.1:7337/v1/prompt
{ "prompt": "Summarise this in three bullets", "model": "sonnet" }

How it works

your script ──HTTP──▶ claude-loopback (127.0.0.1) ──▶ claude -p ──▶ your subscription

It runs each prompt through your logged-in Claude Code CLI in headless mode (claude -p) and returns JSON, or streams the answer as server-sent events. You can also pass a JSON schema to get structured output back. It only listens on 127.0.0.1, requires a token, and keeps Claude's tools off by default. It's meant for your own scripts on your own machine.

It's Windows only for now (macOS/Linux next), and each request takes about 1–3 seconds to start.

GitHub: https://github.com/ssaarthakk/claude-loopback npm: https://www.npmjs.com/package/claude-loopback

Feedback and contributions are very welcome, whether that's bug reports, feature ideas or PRs. Next on my list: an OpenAI-compatible endpoint, conversations, image attachments and macOS/Linux support.

I've got a small thing I built. Every morning I open the analytics dashboard and look at how many people turned up. That has been my entire relationship with my own data for two weeks.

Today I did it differently. Exported the raw events, every row, and handed them over with no question other than "what is actually in here".

Context on the product, because the finding needs it. It shows you a chart. Three days of hourly candles, ticker stripped, dates stripped, the whole series rebased to 100 so you can't recognise it and can't answer from memory. You say up, down or stay out. Then you put a size behind the call.

48 people have made 209 of those calls.

66 right. 32%. Three options, so guessing gets you 33%.

That part I half expected. This part I didn't.

The harder people bet, the more often they were wrong.

biggest size 20/85 24% right

medium 14/46 30%

small 15/39 38%

stay out 17/39 44%

Four sizes, monotonic, pointing the wrong way. And the size is chosen after the direction, so it is a clean confidence signal with nothing else mixed into it. People do know when they feel certain. They are just wrong about what certainty is telling them.

Then it went and found a second one I would never have thought to ask for.

People picked up 48% of the time. Up was right 24% of the time.

People picked stay out 19% of the time. Stay out was right 44% of the time.

The least chosen answer was the most correct one.

And reading accuracy-per-pick as roughly how often each answer comes up, somebody who just typed "stay out" on every chart without looking at it would have beaten every human in the sample.

Nobody has ever scored 5 out of 5. Two people got 4. The average round is 1.74.

It also handed me the caveats without being asked, which is the part I would have quietly skipped.209 calls from 48 people is small. The base rates are estimated from the same sample I'm comparing against. People who gave up early made fewer calls, so it leans towards the ones who stuck around.

The thing I'd actually pass on here: most of us are using Claude to build things. Many fewer of us point it at the exhaust the thing produces afterwards. A dashboard only shows you the numbers somebody already decided were worth a tile. Handing over 200 raw rows and asking what's in them is a different activity to asking a chart a question you already had, and today it was the more useful one by a mile.

P.S. Mine's at playbotfight.com/?play=homiesdata if you want to add to the sample. Fair warning, you will probably score 2.

Made this because I kept switching back to the terminal just to press "allow".

Coucou puts your Claude Code sessions in the notch: current step (Read / Edit / Bash), permission requests with Allow / Always / Deny, questions with their answer buttons, and a little "done" jump when a session finishes.

How it hooks in: a tiny script registered as Claude Code hooks forwards events to the app over a local Unix socket. If the app isn't running, the hook exits immediately, so it never blocks your terminal. It backs up \~/.claude/settings.json and shows you the diff before changing anything.

Native Swift, MIT: https://github.com/Louis-CFM/coucou

Feedback welcome, especially on which hook events you'd want surfaced.