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 valory-xyz/open-autonomy --skill audit-resiliencegit clone --depth 1 https://github.com/valory-xyz/open-autonomyWrote 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/valory-xyz/open-autonomy/audit-resilience)<a href="https://agentmods.dev/skills/valory-xyz/open-autonomy/audit-resilience"><img src="https://agentmods.dev/badge/skills/valory-xyz/open-autonomy/audit-resilience/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/valory-xyz/open-autonomy/audit-resilience"><img src="https://agentmods.dev/badge/skills/valory-xyz/open-autonomy/audit-resilience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 5 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
- medium Tool Misuse · line 588 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 758 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 781 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 1054 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 588 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Excessive Agency · line 590 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00037 | $0.13662 |
| Opus 5 | $0.00018 | $0.06831 |
| Sonnet 5 | $0.00007 | $0.02732 |
| Haiku 4.5 | $0.00004 | $0.01366 |
Grade A, and why
audit-resilience 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 12d 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.
#### Stack 2: Direct path (`requests.get` / `requests.post`) How it starts
The opening of the file, as written. The whole thing — 1,067 lines — stays where its author put it; the contents beside it link to each section on GitHub.
External Request Resilience Audit
You are an expert resilience auditor for open-autonomy agent services. Your job is to discover every external HTTP request the service makes, systematically test each failure mode, trace how failures propagate through the FSM, classify operational impact, and produce a prioritized fix plan.
Open-autonomy is a Python framework for creating decentralized multi-agent systems. Source and docs: https://github.com/valory-xyz/open-autonomy
How to Use Arguments
- If
$ARGUMENTSis provided, audit only those paths (e.g.packages/valory/skills/decision_maker_abci) - If
$ARGUMENTSis empty, discover and audit all skills, connections, and handlers underpackages/ - Multiple paths can be space-separated
Framework HTTP Architecture Reference
This section encodes the domain knowledge you need. Do NOT rely on external documentation — use this as your ground truth.
Three HTTP Stacks
Open-autonomy services use three distinct HTTP stacks. You must identify which stack each external call uses, because error handling is completely different.
Stack 1: Framework path (get_http_response via BaseBehaviour)
Used by behaviours that call yield from self.get_http_response(...).
- Returns an
HttpMessagewithstatus_code,status_text,body - Unreachable / DNS / timeout: the HTTP client connection catches ALL exceptions and returns
status_code=600with the traceback inbody ApiSpecs.process_response()then attempts JSON parse on body:- JSON decode error → returns
None(logs error) - Key/index mismatch in response structure → raises
UnexpectedResponseError→ caught → returnsNone - Does NOT check status_code — a 500 with valid JSON body will be parsed and keys extracted normally
- JSON decode error → returns
- Common retry pattern via
_handle_response()in querying behaviours:res is None→ increments retries, sleeps withbackoff_factor^retries_attempted, setsFetchStatus.FAILwhen retries exceededres is not None→ resets retries, returns data
- The sleep is cooperative (
yield from self.sleep()). The round timeout fires via Tendermint'supdate_time()on the next block. The timeout event transitions the FSM, but the sleeping behaviour continues until it yields — it just becomes irrelevant because the round has moved on.
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.
- 12d ago First seen · 1,067 lines · 37 tokens per session scan A 83d1a433420f
audit-resilience is a skill published in the GitHub repository valory-xyz/open-autonomy (127 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 13,662 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…