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 triage-securitygit 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/triage-security)<a href="https://agentmods.dev/skills/valory-xyz/open-autonomy/triage-security"><img src="https://agentmods.dev/badge/skills/valory-xyz/open-autonomy/triage-security/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/triage-security"><img src="https://agentmods.dev/badge/skills/valory-xyz/open-autonomy/triage-security.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 Tool Misuse · line 817 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 827 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Output Handling · line 1213 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00141 | $0.33814 |
| Opus 5 | $0.00071 | $0.16907 |
| Sonnet 5 | $0.00028 | $0.06763 |
| Haiku 4.5 | $0.00014 | $0.03381 |
Grade A, and why
triage-security 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 10d 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 -sf "https://cwe.mitre.org/data/definitions/${CWE_NUM}.json" \ How it starts
The opening of the file, as written. The whole thing — 2,045 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage security alerts (Dependabot + Code Scanning)
Walk every open security alert on the current repo from both Dependabot (/repos/{r}/dependabot/alerts) and Code Scanning (/repos/{r}/code-scanning/alerts). For each alert, classify by whether it is reachable from production code and then whether the bug's threat model preconditions are satisfied by this codebase's actual usage. Then act in one pass:
| Source | Classification | Confidence + extras | Action |
|---|---|---|---|
| Dependabot | Production-reachable AND exploit-applicable | any | Open tracking issue, leave Dependabot alert open. |
| Dependabot | Production-reachable but exploit NOT applicable — cli-tool | high | Dismiss with inaccurate (+ audit issue per §3.1c). |
| Dependabot | Production-reachable but exploit NOT applicable — framework / scaffold + §2.5.6b passes | high | Dismiss with inaccurate (+ audit issue). |
| Dependabot | Production-reachable but exploit NOT applicable — moderate/low conf OR framework + §2.5.6b fails | — | Open issue + needs-human-review. Do NOT dismiss. |
| Dependabot | Test / dev / CI-only import path | n/a | Dismiss with not_used (+ audit issue). |
| Code Scanning | Rule matches RULE_HUMAN_REVIEW_PATTERNS (cert/TLS bypass, injection in prod, hardcoded secrets non-test, auth/authz, RCE/deserialization, path traversal) |
any | Open issue + needs-human-review. Never auto-dismiss this rule class. |
| Code Scanning | Applicable — flagged code is reachable from prod entry point AND §2.5 preconditions hold | any | Open tracking issue, leave code-scanning alert open. |
| Code Scanning | NOT applicable (false positive) — cli-tool + §2.5 ruled preconditions absent | high | Dismiss with false positive (+ audit issue). |
| Code Scanning | NOT applicable — framework/service archetype OR moderate/low confidence | — | Open issue + needs-human-review. Do NOT dismiss. |
| Code Scanning | Flagged file is under tests/ / PKG_TEST_DIRS |
n/a | Dismiss with used in tests (+ audit issue). |
| Either source | Unclassifiable | n/a | Skip. stderr line for manual review. Never auto-dismiss without evidence. |
Conservative defaults: when uncertain, open the issue. A false-positive issue is cheap to close; a false-negative dismissal hides a real vulnerability. won't fix (code-scanning) and tolerable_risk (Dependabot) are never set by the skill — those are maintainer-only risk-accept calls.
Three paths to autonomous dismissal:
- Dependabot: cli-tool + high confidence + preconditions absent →
inaccurate - Dependabot: framework/scaffold + high confidence + §2.5.6b structural-impossibility passes →
inaccurate - Dependabot: test/dev-only import path (Signal C) →
not_used - Code-scanning: file under tests/ →
used in tests - Code-scanning: cli-tool + high confidence + §2.5 preconditions absent + rule NOT in
RULE_HUMAN_REVIEW_PATTERNS→false positive
Every dismissal produces a closed audit-trail issue (§3.1c) labelled security-audit. The 280-char dismissed_comment carries a one-line summary + audit-issue URL pointer.
This skill runs fully autonomously on invocation — it mutates GitHub state (dismisses alerts, opens issues). Do not invoke from conversational context; require explicit /triage-security.
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.
- 10d ago First seen · 2,045 lines · 141 tokens per session scan A ab7ced1f7540
triage-security is a skill published in the GitHub repository valory-xyz/open-autonomy (127 stars, last pushed 13d ago), licensed Apache-2.0. It adds 141 tokens to every session and 33,814 once invoked, about $0.0007 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
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
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…