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 skills add bidewio/better-openclaw --skill infisical-secretsgit clone --depth 1 https://github.com/bidewio/better-openclawWrote 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/skills/bidewio/better-openclaw/infisical-secrets)<a href="https://agentmods.dev/skills/bidewio/better-openclaw/infisical-secrets"><img src="https://agentmods.dev/badge/skills/bidewio/better-openclaw/infisical-secrets/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bidewio/better-openclaw/infisical-secrets"><img src="https://agentmods.dev/badge/skills/bidewio/better-openclaw/infisical-secrets.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00368 |
| Opus 5 | $0.00006 | $0.00184 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
infisical-secrets scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "{{INFISICAL_URL}}/api/v3/secrets/raw?workspaceId=<ws_id>&environment=dev" \ The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 48 lines · 13 tokens per session scan A 321bea3af61f
infisical-secrets is a skill published in the GitHub repository bidewio/better-openclaw (58 stars, last pushed 22d ago), with no licence file. It adds 13 tokens to every session and 368 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
performing-kubernetes-etcd-security-assessment
Assess the security posture of Kubernetes etcd clusters by evaluating encryption at rest, TLS configuration, access controls, backup encryption, and network isolation.
js-secrets-extraction
Analyze JS bundles and source maps for hardcoded secrets, API keys, JWTs, and internal endpoints.
google-dorks-catalog
High-precision Google dorks for exposed configs, secrets, and credentials -- real-world validated.
ship-safe
Run a full security audit on this project — 16 agents scan for secrets, injections, auth bypass, SSRF, supply chain, Supabase RLS, MCP security, agentic AI, RAG poisoning, PII compliance, and more. Use when the user wants a security audit, vulnerability scan, or asks if their code is safe to ship.
ship-safe-baseline
Manage your security baseline — accept current findings as known debt, then only report new regressions on future scans. Use when the user wants to adopt security scanning incrementally or suppress existing findings.
ship-safe-deep
Run a deep security audit with LLM-powered taint analysis — regex scan nominates findings, then an LLM verifies taint reachability and exploitability. Use when the user wants thorough, high-confidence results with fewer false positives.