authsome

分类: 工具与效率 | 上传者: agentrhq | 下载: 0 | 版本: v1.0（最新）

使用它来访问外部服务/API：Github/Gmail/Stripe 等，或者运行任何进行出站 HTTP 调用的 bash 命令、脚本或curl/wget 时。直接发出 HTTP 请求，网关自动注入凭据。 --- # Authsome 您的出站 HTTPS 流量通过 Authsome 进行透明代理，Authsome 是一种将存储的凭据作为 HTTP 标头注入的代理服务。您永远不会直接看到或处理凭证值。 ## 如何访问外部服务您可以直接通过 HTTP 访问外部 API。 OAuth 应用程序（Gmail、GitHub、Google 日历、Google Drive 等）和 API 密钥服务均可通过网关使用。只需将“authsome run --”附加到任何 bash 命令即可发出请求；如果应用程序已连接，网关会注入凭据。 ## 发出请求调用真实的API URL。网关拦截请求并自动注入凭据。 ```bash authsome run -- <command> authsome run --curl -s "https://api.github.com/user/repos?per_page=10" authsome run -- python my_agent_script.py ``` 标准 HTTP 客户端（curl、fetch、requests、axios、Go net/http、git）都自动遵循 `HTTPS_PROXY` 环境变量。您不需要设置任何身份验证标头。 --- ## 登录流程 - 通过 Bash 自己运行 `authsome login <provider>` — 不要要求用户运行它。浏览器在他们的机器上打开；他们无需接触终端即可完成 OAuth。 - 几秒钟后使用“authsome list”轮询登录状态 - **如果已连接** - 正常进行。 - **如果尚未连接** — 向用户显示身份验证 URL，要求他们在浏览器中完成登录，并在完成后返回报告。用户确认后，再次运行“authsome list”以验证连接，然后再继续。 --- ## 当请求失败时 ### 如果代理计算机上未安装 authsome：使用 `uv tool install authsome` 安装 authsome 仅当 uv tool 安装失败时，使用后备：`pipx install authsome` 或 `uvx authsome@latest <

更新日志: Source: GitHub https://github.com/agentrhq/authsome

目录结构

当前层级: tree/main/skills/authsome/

📁 references/
- 📄 adding-provider.md 1.5 KB
- 📄 feedback.md 2.7 KB
📄 SKILL.md 4.4 KB

SKILL.md

---
name: authsome
version: 0.2.0
description: |
  Use this to access external services/APIs: Github/Gmail/Stripe etc. or when running any bash command, script, or curl/wget that makes outbound HTTP calls. Make HTTP requests directly and the gateway injects credentials automatically.
---

# Authsome

Your outbound HTTPS traffic is transparently proxied through the Authsome,
a proxy service that injects stored credentials as HTTP headers. You never
see or handle credential values directly.

## How to Access External Services

You have direct HTTP access to external APIs. OAuth apps (Gmail, GitHub,
Google Calendar, Google Drive, etc.) and API key services are all available
through the gateway. Just make the request by appending `authsome run -- ` to
any bash command; the gateway injects credentials if the app is connected.

## Making Requests

Call the real API URL. The gateway intercepts the request and injects
credentials automatically.

```bash
authsome run -- <command>
authsome run -- curl -s "https://api.github.com/user/repos?per_page=10"
authsome run -- python my_agent_script.py
```

Standard HTTP clients (curl, fetch, requests, axios, Go net/http, git) all
honor the `HTTPS_PROXY` environment variable automatically. You do not need
to set any auth headers.

---

## Login Flow

- Run `authsome login <provider>` via Bash yourself — do NOT ask the user to
  run this. The browser opens on their machine; they complete OAuth without touching
  the terminal.
- Poll the status of the login using `authsome list` after a few seconds
  - **If connected** — proceed normally.
  - **If not yet connected** — display the authentication URL to the user, ask them to complete the login in their browser, and report back once done. Once the user confirms, run `authsome list` again to verify the connection before continuing.

---

## When a Request Fails

### If authsome is not installed on the agent's machine:

Install authsome using `uv tool install authsome`

Only when uv tool install fails, use fallback: `pipx install authsome` or `uvx authsome@latest <command>` for one-off use (say when running inside sandboxed environments).

### If you get an authentication error (401, 403) follow this decision tree:

**1. Run `authsome list` to see all providers and their connections**

**2. If relevant provider exists but it has no connections → start the [login flow](#login-flow)**

If there is a login error due to wrong client id/client secret you can delete the provider via `authsome remove <provider>` and start the [login flow](#login-flow)

**3. If relevant provider exists and it is connected**

For 401 error → you need to re-login, creds have expired
- revoke the creds using `authsome revoke <provider>`
- then start the [login flow](#login-flow)

For 403 error → you need to re-login, with the correct scopes, or missing permissions
**CRITICAL:** Do NOT register a new provider just to add scopes; always use `--scopes` with the existing provider:

```bash
authsome login <provider> --scopes repo,user,gist
```

**4. If relevant provider does not exist, then → add it first and then start the [login flow](#login-flow)**

## Adding a new provider

See [references/adding-provider.md](references/adding-provider.md).

---

## Troubleshooting & Help

If you are unsure of the correct command syntax, need to check available flags, or if a command fails, ALWAYS read the built-in help menus before guessing:

```bash
authsome --help
authsome run --help
```

## Rules

- **Never** say "I don't have access to X" without first making the HTTP
  request through the proxy.
- **Never** use browser extensions, gcloud, or manual auth flows. The
  gateway handles credentials for you.
- **Never** ask the user for API keys or tokens directly. Run `authsome login
  <provider>`. It opens a browser window and captures them directly, so secrets
  never enter the conversation.
- **Never** suggest the user open Gmail/Calendar/GitHub in their browser
  when they ask you to read or interact with those services. You have API
  access. Use it.
- If the gateway returns a policy error (403 with a JSON body), respect
  the block. Do not retry or circumvent it.
- If the skill fails, the goal took too many steps, the CLI behaved unexpectedly,
  or the user asks you to report an issue — file a bug following
  [references/feedback.md](references/feedback.md).
- **Never** ask the user to run commands in their terminal that you can run yourself.

登录后下载/点赞/收藏 ❤ 32 | ★ 0

authsome

目录结构

SKILL.md

举报内容

提示