it's a frontend today. The git hook version is the right next step. Prompt injection catch was legitimate, though the model's response was arguably correct.

▲

sixtyj 10 hours ago | parent | next [-]

Nice.

Is there a length limit? (It should be noted.)

What is the difference between your tool and lets say some skill for an agent?

Doesn’t Vercel have any ingress/egress traffic pricing? (I’ve seen a project running st Mapbox and its owner had to negotiate how to get $10,000 discount after heavy monthly traffic…it wasn’t fun at first but Mapbox forgave it fortunately.)

	▲	M_Carpenter 9 hours ago \| parent [-]
		Thanks! No length limit right now. good call though, will add a note. On Vercel: will checking pricing. For agent skills, this is purpose-built for SRE mental models specifically, blast radius, cascading failures, MTTR impact. A generic agent skill needs significant prompt engineering to get there; this works out of the box for that one workflow. Plus, i plan to expand it further, testing one use case.

▲

purple-leafy 9 hours ago | parent | prev [-]

I mean, what is the actual value add here?

You are effectively just a frontend that injects a prompt and payload and sends it to Claude. Tell us why that’s better than just dropping it into an llm ourselves which is arguably alot safer because we control our IP, whereas your tool could steal IP.

There’s no validation about the payload, it doesn’t even care if you don’t enter a diff?