Proxy authenticated HTTP requests through a user-controlled broker.
npx skills add https://github.com/getsesame/skills --skill sesame
Please help me install this Agent Skill. Skill: sesame Source: https://github.com/getsesame/skills/tree/main/skills/sesame Command: npx skills add https://github.com/getsesame/skills --skill sesame
This skill solves the challenge of managing sensitive API credentials by offloading authentication to a user-controlled broker, ensuring the agent never handles or stores raw auth material.
Use the sesame skill to perform an authenticated GET request to the GitHub API for the current user.
High-intent search queries and answers about installing and using this skill.
Authenticated API calls are proxied through a user-controlled broker that attaches required auth headers server-side. This eliminates the need for agents to manage API credentials directly, ensuring sensitive tokens never reach the agent process.
Managing API authentication for GitHub or Slack is handled by routing HTTP requests through a broker that automatically attaches Bearer tokens or API keys based on target hostnames. The agent performs standard requests while the broker handles auth injection.
Access policy enforcement for proxied HTTP requests allows granular control over which HTTP methods and paths an agent can access on specific hostnames. The broker validates requests against these rules before attaching auth headers and forwarding traffic.
Installing the sesame CLI is required to intercept and broker network traffic. The agent must also be registered with a valid broker URL to establish the secure proxy connection for authenticated HTTP requests.
Transparent egress is achieved by wrapping entire process trees to intercept and broker network traffic. This approach automatically routes outgoing HTTP requests through the authentication proxy without requiring modifications to the underlying application code.
A broker proxy for API authentication should not be used when your application requires direct management of raw auth material. If your architecture cannot route HTTP requests through an external hostname-based broker, this proxy approach will not fit.
getsesameProvision a self-hosted Sesame broker on AWS with IAM and OAuth setup.
trohitgExecute HTTP requests with configurable methods, headers, and JSON bodies.
kagentiConfigure L7 AuthorizationPolicy in Istio Ambient mode with waypoint proxies.
aussiegingersnapAutomate Better Auth integration in Next.js 16 with a Drizzle adapter.
