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-fsmgit 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-fsm)<a href="https://agentmods.dev/skills/valory-xyz/open-autonomy/audit-fsm"><img src="https://agentmods.dev/badge/skills/valory-xyz/open-autonomy/audit-fsm/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-fsm"><img src="https://agentmods.dev/badge/skills/valory-xyz/open-autonomy/audit-fsm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Privilege Escalation · line 746 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Tool Misuse · line 846 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 759 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.00014 | $0.14714 |
| Opus 5 | $0.00007 | $0.07357 |
| Sonnet 5 | $0.00003 | $0.02943 |
| Haiku 4.5 | $0.00001 | $0.01471 |
Grade A, and why
audit-fsm scanned grade A with 2 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 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.
3. Grep the imports of the round module for `time`, `datetime`, `random`, `os`, `requests`, `urllib`, `pathlib`. Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `subprocess.Popen` or process `terminate()` without corresponding `wait()` (creates zombies) How it starts
The opening of the file, as written. The whole thing — 1,062 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit FSM Skill
You are an expert auditor for open-autonomy FSM (Finite State Machine) apps. Your job is to analyse FSM skill code for correctness bugs, safety issues, and configuration problems.
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/registration_abci) - If
$ARGUMENTSis empty, discover and audit all skills underpackages/ - Multiple paths can be space-separated
FSM Architecture Reference
This section encodes the domain knowledge you need. Do NOT rely on external documentation — use this as your ground truth.
Core Abstractions
AbciApp
The state machine definition. Key class attributes:
class AbciApp(Generic[EventType], ABC, metaclass=_MetaAbciApp):
initial_round_cls: AppState # Entry point round class
initial_states: Set[AppState] = set() # Set of possible starting rounds
transition_function: AbciAppTransitionFunction # Dict[AppState, Dict[Event, AppState]]
final_states: Set[AppState] = set() # Terminal rounds
event_to_timeout: EventToTimeout = {} # Dict[Event, float] — timeout scheduling
cross_period_persisted_keys: FrozenSet[str] # DB keys preserved across periods
db_pre_conditions: Dict[AppState, Set[str]] # Required DB keys before initial states
db_post_conditions: Dict[AppState, Set[str]] # Guaranteed DB keys after final states
background_apps: Set[BackgroundApp] = set() # Concurrent background tasks
Critical detail — timeout scheduling: The framework only schedules timeouts for events that appear as keys in a round's transition_function entry. If an event is in event_to_timeout but never appears in any round's transition keys, the timeout is never scheduled and is dead configuration.
_MetaAbciApp Metaclass Validation
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,062 lines · 14 tokens per session scan A 81395c407aae
audit-fsm is a skill published in the GitHub repository valory-xyz/open-autonomy (127 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 14,714 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
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.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
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…
G2 Legend Expert
Expert skill for G2 legend development - provides comprehensive knowledge about legend rendering implementation, component architecture, layout algorithms, and interaction handling. Use when implementing, customizing, or debugging legend functionality in G2 visualizations.