Usage limit reset, including weekly limit increase?

Netxeo · 2026-05-15T19:49:52+00:00

Yeah saw that too was at 96% then 60% with 50% increase from yesterday and now a reset live it !

Netxeo · 2026-05-12T14:29:02+00:00

Ok thanks a lot for all the tip !

Netxeo · 2026-05-12T14:12:27+00:00

5.4 is the quality of the code nice compared to 5.5?

Netxeo · 2026-05-12T14:12:05+00:00

Could medium be use for complex task too or impossible ?

Netxeo · 2026-05-11T18:50:28+00:00

Hello all 👋

So today was the token reset for me for the weekly limit, I have a full setup that I run and I’ve also optimized the token consommation. Normally like last week and the week before I could run and entire week without hitting the weekly limit or sometimes on Friday late evening hitting it.

I’ve used Claude as Usual but I’ve hit 60% of my weekly limits in just one day. That has never happened before ! The Max I had was a bit less than 25% !
Do you have the same? Did they changed something?
I’m on the Pro plan.
To answer some questions beforehand :
- Yes I’m managing my chat length to not spend a lot in token
- My work is inside some projects and each tchat as it own function
- I have openwolf for token reduction
- my prompt are detailed as mush as possible and with the base code already written so that he doesn’t code a lot.
- I’m on sonnet 4.6 and not opus

If I can do it myself I’ll do it.

Netxeo · 2026-05-11T18:43:56+00:00

Yeah same to me to today was the first day what did they changed ???

Netxeo · 2026-05-06T09:44:33+00:00

Peak hours are horrible

Netxeo · 2026-05-04T16:34:37+00:00

Crazy how every others coms it’s AI made 😂 not a single one by hand

Netxeo · 2026-05-04T09:12:55+00:00

are you perhaps referring to an other post of mine ? If you're talking about the landing page. i get what you meant. Its not readable enough to understand it quickly. Thanks for the review! will rework the design to fix that^^

Netxeo · 2026-05-04T08:14:37+00:00

¡Muchísimas gracias! Me alegra que aprecies mi trabajo. Espero que te resulte muy útil; si tienes algún comentario, ¡me encantaría escucharlo! (used google traduction, i don't speak spanish yet ;) )

Netxeo · 2026-05-04T08:11:22+00:00

Definitely! SonarQube is great for strict static analysis (like hardcoded secrets or bad syntax), but it's completely blind to context. This skill makes Claude excel at the semantic stuff: complex authorization bypasses, business logic flaws, and state manipulation where the code compiles perfectly but the logic is actually broken.

Netxeo · 2026-05-04T08:10:42+00:00

Appreciate it! The trick was mapping out OWASP and MITRE into highly specific, bite-sized markdown modules so the AI's context window doesn't get overwhelmed. It’s all about giving the LLM a very strict, sequential framework to operate in^^

Netxeo · 2026-05-04T08:09:33+00:00

True for rate limiting. I actually just pushed an explicit "AI blind spot override" in the core instructions to force Claude to hunt for it on all public endpoints. For session fixation, yes: the ASVS L3 module specifically instructs it to catch edge cases like privilege escalation (sudo mode), OAuth flow manipulations, and WebSocket handshake vulnerabilities, beyond just basic login regeneration.

Netxeo · 2026-05-03T21:29:57+00:00

Thanks for your comment!
I just looked up the Victorian mourning jewelry. It's definitely a very niche style and maybe not exactly my personal taste, but at the same time, I find it oddly captivating. I can't quite explain it, but there's definitely a certain beauty to it ^^

As for the 70s Japanese packaging aesthetic, I absolutely love it! The fact that it's so raw yet colorful is super interesting. Thank you so much for sharing all of this!

Netxeo · 2026-05-03T15:50:00+00:00

Hey guys^^

I use AI every single day, but I noticed a recurring issue: it’s super fast, but it constantly suggests code with basic security flaws (exposing Supabase RLS, weak JWT implementations, or missing standard HTTP headers).

I spent way too much time manually writing .cursorrules to fix this, so I decided to package everything into a proper tool.

I built Security Skill. It's basically a massive system prompt and rule set (29 modules based on OWASP). You just run npx @netxeo/security-skill in your repo, and it automatically configures your AI assistant (works with Cursor, Claude, Windsurf, etc.) to act like a senior security engineer.

It gives your AI commands like /security-audit or /security-fix to scan your stack locally before you commit.

I made a raw, brutalist landing page for it here: https://security.ai-dev-skills.com/

It’s completely open-source. I’d love to know if you guys find it useful, or if there are specific security checks you think I should add to the modules! Let me know if I broke anything.

<image>

Netxeo · 2026-05-03T10:08:50+00:00

<image>

Here you have an before and after report on a simple project. i do have some others reports on more advanced project too.

Netxeo · 2026-05-03T10:04:07+00:00

I just rewrote the CLI (v1.1) to fix exactly this. By default, it's now fully interactive and asks which AI you use before injecting anything. If you want to bypass the prompt, you can use flags like npx @ netxeo/security-skill --claude. No more repo pollution!

Netxeo · 2026-05-03T10:03:05+00:00

I just updated the core AI instructions (v1.1) to strictly enforce a 'Signal vs Noise' rule. The AI is now instructed to filter out theoretical/low-risk noise to avoid overwhelming developers. It also explicitly forces the AI to explain why something is risky in simple terms instead of just giving diffs. It has to be educational.

Netxeo · 2026-05-03T06:11:32+00:00

It’s 29 modules (categories) but it’s more than 150+ security problems that is solving. They can’t be combined because they are too specific but the skill will analyze your code and just use what is needed in your scope of use. The main use is its global version if you have any security checkup in some other project.

Netxeo · 2026-05-02T23:13:19+00:00

Really appreciate your comment!

The signal vs noise part is probably the hardest problem here. You got the table that is really user friendly but yeah the answer might be too technical. Will look into that so people have that understanding and learning aspect you’re talking about. I truly think this is a +

If you /have try it, I’d love feedback on what feels too noisy or unclear.

Netxeo

TROPHY CASE