Developer Tools

An assistant that helps write code sits close to the things you least want copied. A developer pastes a stack trace with a bearer token inside. A prompt asks for a deploy script and gets one that nobody reads closely. Both are ordinary events, and both are what this starter watches for.

Credential shapes in a prompt are masked, and two phrases block the call: private key and production credential. Generated code then meets a sanitizer set to refuse a match instead of flagging it. A snippet that trips a rule never lands in the reply.

Nothing here names which tools an agent may call. Tool call analysis runs on the gateway, and the allow decision stays in your own harness. Wire the assistant to a repository or a deploy path only after you decide what it may touch.

Replies must clear a combined 0.82 with accuracy at 0.80 and relevance at 0.78. Short or single sentence answers fail before a reader sees them. The oversight step is present but unconfigured, which means no escalation happens yet. Pull requests, branch protection and release approval still carry the real weight.

The Cybersecurity Products starter uses the same settings for a different reader. Reach for it when you ship security tooling to customers and hostile input is the product surface. Stay here when the audience is your own engineers and the risk is an unreviewed change.