sigcli-auth-proxy

Proxy HTTP requests with injected SSO or OAuth2 credentials for configured domains.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/Aradotso/devtools-skills --skill sigcli-auth-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sigcli-auth-proxy
Source: https://github.com/Aradotso/devtools-skills/tree/main/skills/sigcli-auth-proxy
Command: npx skills add https://github.com/Aradotso/devtools-skills --skill sigcli-auth-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sigcli-auth-proxy eliminates the risk and friction of manually handling browser SSO sessions and OAuth tokens by enabling AI agents to make authenticated requests without exposing secrets.

Core Features & Use Cases

  • Browser SSO credential extraction: Authenticates via browser-based flows and extracts session cookies for agent usage.
  • OAuth2 token management: Supports OAuth2 Client Credentials with token refresh and secure header injection.
  • Encrypted credential storage and proxying: Encrypts credentials locally with AES-256-GCM and provides a transparent HTTP proxy so agents can reuse authenticated context across many requests.

Use case: An enterprise agent needs to call Jira or internal APIs with user SSO—run sig proxy so all HTTP calls made to configured domains automatically receive the right authentication headers/cookies.

Quick Start

Tell your AI to set up sigcli-auth-proxy by logging in for your SSO domain (for example, sig login https://jira.example.com) and then use sig proxy on a local port for authenticated requests.

Frequently Asked Questions about sigcli-auth-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make authenticated requests to SSO APIs without exposing credentials in prompts?

To make authenticated requests to SSO APIs without exposing credentials, use a transparent HTTP proxy that injects encrypted session cookies or Authorization headers only for configured domains. This prevents leaking secrets in AI prompts or environment variables.

How does an HTTP proxy handle OAuth2 token refresh for long-running agent sessions?

An HTTP proxy handles OAuth2 token refresh for long-running agent sessions by intercepting requests to configured domains and automatically retrieving new access tokens using Client Credentials, then securely injecting the refreshed Authorization headers.

Can AI agents reuse browser SSO sessions for enterprise API access?

Yes, AI agents can reuse browser SSO sessions for enterprise API access. The proxy authenticates via browser-based flows, extracts session cookies, and applies provider-specific rules to inject them into subsequent HTTP calls.

What is the best way to secure local credentials for AI agent HTTP proxying?

The best way to secure local credentials for AI agent HTTP proxying is encrypting them locally with AES-256-GCM. This ensures stored SSO cookies and OAuth2 tokens remain protected while the proxy transparently injects them into requests.

Does transparent credential injection work for specific domains only?

Yes, transparent credential injection works for specific domains only. The proxy requires provider-specific domain rules to ensure authentication headers or cookies are injected exclusively for configured enterprise APIs, preventing unauthorized exposure.