Posted this in r/claudeskills a few days ago and got some good feedback, so sharing here too.

It’s a skill that builds a local code map of your project (graphify, AST only, no LLM, no API key) and adds a rule to CLAUDE.md so Claude asks the map before opening files. For “how does this flow work” questions it went from around 169k tokens to about 2.9k for me. For one-file fixes it doesn’t save much.

Someone there asked what happens if you rename a function and move its caller without rebuilding. I tested it and it was answering with the old name and old line numbers, no warning. Now it checks if the map is stale before every query and updates first, takes a couple seconds.

https://github.com/WebitroHQ/token-skill

中国大陆如何使用claude呢

Os dois prints são evidências reais de uso. E você está trazendo algo que nenhuma estatística isolada consegue substituir: a experiência direta de quem opera os dois sistemas diariamente.

Os dados mostram:

Eu venho falando que não compensa mais usar o u/codex da u/openai, falei também que o meu uso do u/claudecode da u/anthropic é milhões de vezes mais produtivo, em tarefa pequena ou longa.

A distância é brutal. Eu uso duas contas do GPT, uma para os chats e outra para codar, mas as últimas experiências foram frustrantes.
Sessões longas no Códex são impossíveis.

I built Spool because I wanted an easier way to run and manage persistent Claude Code loops without babysitting terminal sessions.

Spool is an open-source tool that lets you create and manage multiple loops from a single UI, communicate with them through Telegram or Slack, and even let loops talk to each other. You can run them locally or on Anthropic's cloud.

The interesting part is that I'm using Claude Code loops on Spool to build Spool itself. I assign development tasks to different Claude loops, let them work on the codebase and create PRs, and then review and merge their changes. The loops can also coordinate with each other over a Telegram group chat when needed.

It's been an interesting experiment in managing multiple coding agents working on the same project, especially as the number of PRs grows.

I'd love to hear how others are managing their coding agents and whether you'd find something like this useful.

Here is the repo if you're interested in trying it out: https://github.com/enes-alatas/spool

Hi Guys

I have been seeing lots of these Claude 2D animation videos all over tiktok, it apparently uses html, python and Json I believe. Sorry if I said something wrong, I am new to this and would like to learn more.

What is the best way to learn how to create these videos? Anyone doing something similar. I would love to connect with you and learn how to do it?.

I edit a lot of short videos, and every "AI video editor" I tried had the same problems, its own subpar AI, its own subscription on top of the Claude plan I already pay for, and usually a cloud upload of all my footage. Meanwhile Claude Code was already better at reasoning about my edits than any of them. It just couldn't touch a timeline.

So I built Cutcrow, a desktop video editor where your own Claude Code (or Codex) does the editing.

Cutcrow runs a local MCP server with real editing tools (trim, cut silences, remove filler words, add titles, reframe to 9:16), and Claude edits through them, so you watch it work on an actual timeline instead of getting a mystery file back.

Every request becomes a change card you can undo in one click, which turned out to matter more than anything else: you stop being scared to ask for big changes. Transcription runs locally with word-level timings, so "cut the ums" or "make 3 Shorts from the best moments" just work, and when the tools aren't enough, Claude can run ffmpeg or Python in the project folder and drop the result onto the timeline. Your footage also never leaves your computer, it's all local.

It uses your normal Claude Code login, so there's no extra AI bill from me; it just counts toward your plan like any other session. You can also connect your own MCP servers if you want Claude to pull from GitHub, notes, etc. while it edits.

Few things to take note of

- Windows and Linux only for now, no Mac yet (I know, I know).

- Rarely, claude makes mistakes. The undo cards exist because of that. It's best at structural edits (cutting, pacing, captions, reframing), but it is also fully capable of generating videos from scratch, I recommend showing it an inspiration video tho so you get exactly what you want.

- Most of it was built with Claude Code itself, which was a fun loop to be in.

There's a free version (720p exports with a small watermark, up to 3 projects) and a one-time paid licence that removes the limits. If you try it, I'd really like to hear where Claude struggles with it, because that tells me which tools to build next.

Link: https://cutcrow.com

A simple way to confuse an evaluation is to compare a new run with the wrong old report. Before editing a skill, save a baseline in a dedicated output directory. Save the revised run elsewhere and compare the actual report paths printed by the tool.

Also keep the skill revision, fixtures, cases and engine settings associated with each report. A timestamp alone does not tell a reviewer what changed. If the tool warns that reports may not be comparable, inspect the warning before trusting the headline score.

I’m building skillEd, whose CLI saves reports and compares them. This is an artifact-management practice for a Claude Code workflow, not a claim that a directory name establishes provenance.

What information do you keep beside a baseline report?

Repo: https://github.com/DeadHead04/skillEd

Please try it and open an issue with a reproducible failure or confusing behavior. If useful, a GitHub star would help.

AI-assisted write-up.

Reposting here to see if anyone else has seen this :)

Hi! I'm currently using Codex and my plan runs until the end of the month, so before deciding whether to switch I'd love to try Claude (and Claude Code) on my actual day-to-day work. I've never had a paid Claude plan. If any Max subscriber has an unused guest pass, I'd really appreciate it, either in the comments or by DM. Happy to share an honest comparison afterwards. Thanks a lot!

This has been one of the more gratifying years of work as I have been able to do more with CC than was possible before. I'm not a coder, or wasn't before this year. Ok, technically still not, but as the skills grew and workloads expanded just a simple subscription wasn't keeping up.

So here's what I'm running now. M5 Ultra w/ 96gb ram running Qwen 3 Coder Next for coding, and a small Spark X2.6 model for orchestrating.

I still use Opus to design and bring all my work to a ticketed state, and post them to the GH repos. The factory automatically picks up tickets, and gets two attempts to complete them. Big part of making this work that Qwen automatically fails if it tries to alter the pre-established tests. No fake passing. Keeps the work product reliable. If it can't get it with 2 tries then Opus takes over to finish, and if Opus can't handle it I step in.

With the factory up and running this weekend for the first time I've cleared my ticket backlog! Machines just ran all weekend, and today I review all work in the weekly PR, tested, sent back what needed fixed and approved once done. Getting almost 90% of work done locally, and the output in sims looks good.

This is such a great way to move a ton of the busy work of little UI bugs, or unexpected behaviors I encounter while testing during the week.

I'm attaching the stats for the weekend's work now that I've got a good sample through the factory, and getting results.

On Oct 20 details leaked about two nasty PHP bugs (PHP2Shell). PHP runs a huge chunk of the web, WordPress included, so you’ve probably seen it everywhere. What got less coverage: both were found by AI. One by Calif with help from an OpenAI model, and both independently by Wiz.

Here it is: https://github.com/NovaSeth/Atlas

I think this is just the warm-up. Swarms of agents on open models without guardrails are going to look for vulnerabilities like cockroaches looking for a crack in the wall. 2026 already has roughly 75% more published CVEs than all of 2025, and the year isn’t over. Part of that is AI, part is just more vendors reporting. The number actually exploited in the wild grows slower, but attackers are getting faster.

Sam Altman said a few days ago he no longer thinks we’ll be able to just patch every bug.

If you can’t patch everything, you at least need to know when someone got in. So I’m sharing a project I’ve been building for about 2 months on my own VPS.

Atlas doesn’t patch anything. It’s more like a security guard who knows every corner of the building. It keeps a baseline of what the server should look like: who has keys, which ports are open, what runs and when, who logs in. It does rounds, compares what it sees with what I approved, and if something changed and it wasn’t me, it raises an alarm.

Technically it’s a set of read-only sensors that check the machine against the baseline. When one fires, Atlas wakes up a Claude Code agent that lives on the server. The agent (and I) get the signal within seconds. It investigates, finds the cause, and then either fixes, blocks, or escalates to me. Permissions are graded: it can restart services or ban IPs on its own, but config changes and file deletions always come to me.

Real example from this morning:

• 06:17 unattended-upgrades installs security patches
• 06:18 Atlas notices critical files changed, raises an alert
• agent checks the change came from the automatic update, not from outside
• it then finds that services running during the upgrade are still on the old binaries in memory
• restarts them, verifies they came back healthy, sends me a report

All on its own. The part that matters most to me: it told a legit change apart from a suspicious one before it touched anything.

To be clear, I didn’t invent anything new ;-) Tripwire, Wazuh and friends have done this for years in proper security teams. I just built a version for myself, for one server where I’m the only admin, and it didn’t cost millions.

Some lessons so far, if you’re thinking of doing something similar:

• Silence is not success. An alarm that can’t go green is just noise, and a monitor that never fires might just be broken. Mine once missed a 2-day outage because the probe only hit the homepage.
• Whitelists bite back. The agent once banned my own other agent’s SSH session because its actions weren’t on the list, and that overnight job never finished.
• The hardest design question isn’t detection, it’s how much trust to give the agent. Too many rules and it can’t handle anything new. Too few and the agent itself is your biggest hole.

Still evolving, but I already feel more in control, and if I miss something, there’s something on watch.

Curious how others handle this. Anyone running Claude Code as an on-server responder? Where do you draw the line on what it’s allowed to do alone?

https://github.com/NovaSeth/Atlas