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.
npx agentmods add agents/connected-mate/corporate-launcher/api-probe-subagentgit clone --depth 1 https://github.com/Connected-Mate/corporate-launcherWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/connected-mate/corporate-launcher/api-probe-subagent)<a href="https://agentmods.dev/agents/connected-mate/corporate-launcher/api-probe-subagent"><img src="https://agentmods.dev/badge/agents/connected-mate/corporate-launcher/api-probe-subagent.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00046 | $0.00849 |
| Opus 5 | $0.00023 | $0.00425 |
| Sonnet 5 | $0.00009 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
api-probe 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 4d ago.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
api-probe subagent
What
Runs scripts/api-probe.py against a corporate AI gateway and returns a 3-line
summary to the main conversation. All network noise, JSON payloads, and TLS
chain details stay in the fork context.
Input
Caller must provide:
--url <BASE_URL>— gateway base, e.g.https://ai-gateway.corp.example/v1--backend <NAME>— one ofauto|anthropic|openai|azure|vertex|litellm|bedrock-proxyAPI_TOKEN— auth token exported as env var only, never passed on the command line by the caller and never echoed in shell history.
Workflow
-
Read the token from the env var
API_TOKEN. If empty, returnFAIL: missing API_TOKEN env varand stop. -
Run the probe in a single bash invocation that pulls the token from the environment at exec time:
API_TOKEN="$API_TOKEN" python3 "${CLAUDE_SKILL_DIR}/scripts/api-probe.py" \ --url "<URL>" \ --backend "<BACKEND>" \ --token "$API_TOKEN" 2>&1Capture exit code and stdout. The token lives in argv only inside the forked process; it never appears in our reply.
-
Parse the JSON report (
ok,latency_ms,models_available,tls.expires,tls.cert_issuer,warnings,error). -
Emit a 3-line summary to the parent:
Gateway reachable (245ms), 6 models available, TLS cert valid until 2027-01-15 Backend: openai (bearer-token), warnings: none Token preview: sk-a...x9k2 — OK
Exit-code mapping
| Code | Meaning | Remediation hint to surface |
|---|---|---|
| 0 | OK | None — emit success summary. |
| 2 | auth failure (401/403) | Token expired or wrong header style — re-issue from IdP. |
| 3 | network / DNS / timeout | Check VPN, corporate proxy (HTTPS_PROXY), URL typo. |
| 4 | TLS cert error | Install corp CA bundle, set REQUESTS_CA_BUNDLE. |
| 5 | bad CLI args | Verify --url scheme is http(s):// and host is non-empty. |
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.
- 4d ago First seen · 92 lines · 46 tokens per session scan A 9c470c0274eb
api-probe is an agent published in the GitHub repository Connected-Mate/corporate-launcher (3 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 849 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
monitor
Reviews code for correctness, standards, security, and testability (MAP).
evaluator
Evaluates solution quality and completeness (MAP).
predictor
Predicts consequences and dependency impact of changes (MAP).
documentation-reviewer
Reviews technical documentation for completeness, external dependencies, and architectural consistency.
reflector
Extracts structured lessons from successes and failures.
final-verifier
Adversarial verifier with Root Cause Analysis (Ralph Loop).