 %%%@=..        #*****@
 %%+::=.        ==@***.
 %:::::=       #====@..
  #=        @##===#         @=
*==##=    @**#====###    #**#==#=
*#===#    ***@======     ***#===#
 @#       @@*@===#   @%@   @@=
         %+%#*#     @%%++.=
          ++==       %+++.

agents / code

sharp-edges-analyzer

what it does

Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.

tools it asks for

Reads files

by trailofbits · version 1 · license CC-BY-SA-4.0

We imported this agent from its author’s repository. Is this yours? Claim this listing

Verified Before and after: 2 models 1 try per case View source Install from your agent Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the agent’s instructions as its system prompt and once without. Neither could use a tool. Read both and judge for yourself.

Compare the answers

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 7 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 7 Nov 2026

The tasks

written by Carte Blanche

example-1

“I'm designing a small Python crypto helper library. Here's the main interface: `encrypt(data, key, mode='ECB', iv=None)` and `verify_token(token, secret, check_signature=True)`. If iv is None, it silently uses a zero IV. Can you review this for footguns and dangerous defaults, and suggest how to redesign it so the safe path is the easy one?”

example-2

“Our team is about to ship a YAML-based config for our deployment tool. Sample: `auth: {enabled: false, tls_verify: false, allow_origins: '*'}` is the default template, and any unknown keys are silently ignored. Debug mode is on unless `debug: false` is set. Please analyze this config design for misuse potential and tell me which defaults and behaviors people are likely to get wrong.”

Install

Download the .zip and unzip it. Put sharp-edges-analyzer.md here:

Claude Code~/.claude/agents/Every project. For one project only, use .claude/agents/ inside it. It gives the agent the tools it asks for, and no others.

Cursor~/.cursor/agents/Cursor also reads the Claude Code folder above. It has no tools field, so it gives every agent every tool, whatever this one asks for.

CodexCodex’s custom agents are TOML files, not Markdown, so this agent doesn’t install there.

Keep its license file beside it, as sharp-edges-analyzer.LICENSE: a name that doesn’t end in .md, since every .md file there is read as an agent.

Then start a new session and ask for it by name. Folders checked 6 November 2026.

Or install from your agent: ask it to install sharp-edges-analyzer from Carte Blanche.