| name | api-relay-audit |
| description | Use when auditing third-party AI API relays, LLM proxies, gateways, or API-key resale services locally before trusting coding, tool, production, or wallet-sensitive traffic. |
| version | 2.4.0 |
| author | Toby Bridges |
| license | AGPL-3.0-only |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["security","red-teaming","ai-safety","api-relay","web3"],"related_skills":[]}} |
| required_environment_variables | [{"name":"API_RELAY_AUDIT_KEY","prompt":"API relay key","help":"Use a temporary or low-scope key for the relay being tested.","required_for":"Running relay audits without pasting secrets into chat"}] |
API Relay Audit for Hermes Agent
Overview
This skill runs api-relay-audit, a zero-dependency 14-step security audit for third-party AI API relays and proxy services. It checks relay behavior while keeping API relay audit, prompt injection audit, model substitution signals, and Web3 relay audit as separate query families with separate evidence boundaries.
Use the standalone audit.py path by default. It only needs Python 3 and curl, which makes it suitable for local Hermes terminal sessions and sandboxed execution. On Windows, run the POSIX shell recipes from Git Bash or an equivalent shell; direct python audit.py ... invocations also work from PowerShell when the environment variables are set.
When to Use
- The user asks whether an AI API relay, proxy API, resale key, or "API relay" is safe.
- The user provides a relay base URL and wants an evidence-based risk report.
- The user suspects hidden prompts, identity substitution, response tampering, context truncation, tool-call/package substitution, or stream anomalies.
- The user wants to audit Web3/wallet safety behavior with
--profile web3 or --profile full.
Do not use this skill for general model benchmarking, provider price comparison, or legal/security certification. The output is a technical audit report, not a guarantee that a service is safe.
Keep these query families separate:
| Query family | Use when | Profile / evidence boundary |
|---|
| API relay audit | The user wants a local report for a relay, mirror, gateway, LLM proxy, or resale API. | Default general; report is evidence, not certification. |
| Prompt injection audit | The user asks about hidden prompt injection, prompt leakage, instruction override, or extraction behavior. | Steps 3-6; do not publish private prompts or secrets. |
| Model substitution signals | The user suspects model identity, route, latency, or upstream channel mismatch. | Signals from Steps 5, 10, 13, and 14 require corroboration; self-ID and fingerprints are not standalone provider proof. |
| Web3 relay audit | The user is testing wallet-sensitive agent workflows. | Use --profile web3 or --profile full; Step 11 is profile-gated. |
Install or Share
After this file is merged to the public repository, Hermes users can install it as a tap skill:
