authsome

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

authsome scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

.claude-plugin/marketplace.json · 28 lines

What it actually says

{
  "name": "authsome",
  "owner": {
    "name": "Agentr",
    "url": "https://agentr.dev"
  },
  "metadata": {
    "description": "Local OAuth2 and API-key credential broker for AI agents.",
    "version": "1.0.0"
  },
  "plugins": [
    {
      "name": "authsome",
      "source": "./skills/authsome",
      "description": "Login once, credentials live in an encrypted local vault, a local proxy injects them into outbound requests so the agent's env never holds raw keys. 45 providers preconfigured (14 OAuth2, 31 API key).",
      "version": "1.0.0",
      "author": {
        "name": "Agentr",
        "url": "https://github.com/agentrhq"
      },
      "homepage": "https://authsome.ai",
      "license": "MIT",
      "keywords": ["auth", "oauth2", "credentials", "agent-identity", "broker"],
      "category": "auth"
    }
  ]
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other plugins, from other repositories