Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计提醒

ioc-analysisIOC 分析

Agent Skill

ioc-analysis 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

353

周安装

15

GitHub Stars

4

下载量

124
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ioc-analysis(IOC 分析)
来源仓库:https://github.com/alphaonedev/openclaw-graph
仓库路径:skills/ioc-analysis
安装命令:
npx skills add https://github.com/alphaonedev/openclaw-graph --skill ioc-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/alphaonedev/openclaw-graph --skill ioc-analysis

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在需要整理仓库状态、代码变更或协作事项时使用。
  • 可结合来源仓库和 README 核验具体用法。
  • 安装命令:npx skills add https://github.com/alphaonedev/openclaw-graph --skill ioc-analysis。
  • 建议确认权限范围、维护状态及是否触发联网或命令执行。

SKILL.md

ioc-analysis

Purpose

This skill enables the analysis of indicators of compromise (IOCs), such as IP addresses, domains, file hashes, and URLs, to identify potential threats, correlate them with known attack patterns, and generate actionable insights for cybersecurity defense.

When to Use

  • Use during incident response when a suspicious artifact (e.g., an IP from a log) needs immediate verification.
  • Apply in proactive threat hunting to scan for IOCs in network traffic or endpoint data.
  • Integrate into automated workflows for daily security monitoring of external feeds.

Key Capabilities

  • Parse and enrich IOCs using threat intelligence databases, including IP geolocation, domain reputation, and hash matching.
  • Detect anomalies by cross-referencing IOCs against predefined threat feeds or custom rulesets.
  • Generate reports with severity scores, related threats, and recommended mitigations.
  • Support bulk analysis for processing multiple IOCs in a single operation.
  • Integrate with logging systems to automate alerts based on analysis results.

Usage Patterns

Always initialize the skill with authentication via the $OPENCLAW_API_KEY environment variable. Use the CLI for quick queries or the API for programmatic integration. For CLI, pipe inputs from files; for API, handle requests in loops for batch processing. Validate IOC formats before submission (e.g., IPv4 as dotted decimal). Structure workflows to check for errors after each call and retry transient failures.

Common Commands/API

  • CLI Command: Run openclaw ioc-analysis --ioc 192.168.1.1 --type ip --output json to analyze an IP; add --feed custom for a specific threat feed.
  • CLI Flag Details: Use --timeout 30 to set request timeout in seconds; --verbose for detailed logs.
  • API Endpoint: POST to https://api.openclaw.com/v1/ioc-analysis with JSON body like {"ioc": "example.com", "type": "domain"}.
  • API Authentication: Include header Authorization: Bearer $OPENCLAW_API_KEY.
  • Config Format: Use JSON for configurations, e.g., {"feeds": ["virustotal", "alienvault"], "threshold": 0.7} in a file passed via --config path/to/config.json.
  • Code Snippet (Python): import os import requests api_key = os.environ.get('OPENCLAW_API_KEY') response = requests.post('https://api.openclaw.com/v1/ioc-analysis', headers={'Authorization': f'Bearer {api_key}'}, json={'ioc': '8.8.8.8', 'type': 'ip'}) print(response.json()['threats'])
  • Another Code Snippet (Shell): export OPENCLAW_API_KEY=your_key_here curl -H "Authorization: Bearer $OPENCLAW_API_KEY" -X POST https://api.openclaw.com/v1/ioc-analysis -d '{"ioc": "badfile.exe", "type": "hash"}'

Integration Notes

Integrate by importing the OpenClaw SDK in your application; for example, in Python, use from openclaw import IOCAnalyzer. Set up webhooks for real-time notifications by configuring {"webhook_url": "https://your.endpoint.com/alerts"} in the API request body. Combine with other blue-team skills by chaining outputs, e.g., pipe IOC results to a threat-detection skill. Ensure compatibility by matching API versions (e.g., v1) and handle rate limits with exponential backoff. For containerized environments, mount config files as volumes and inject $OPENCLAW_API_KEY via secrets.

Error Handling

Check HTTP status codes after API calls; for 401, prompt for re-authentication. For 429 (rate limit), implement a retry loop with delays: wait 5 seconds and retry up to 3 times. Parse JSON errors for specifics, e.g., if "error": "Invalid IOC format", validate inputs first using regex (e.g., for IPs: r'^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$'). In CLI, capture stderr and exit codes; use try-except in code snippets to log exceptions and fallback to default actions.

Concrete Usage Examples

  1. Example 1: Analyze a Suspicious IP During an incident, query an IP from a firewall log: Run openclaw ioc-analysis --ioc 192.168.1.100 --type ip --feed virustotal. This returns JSON with threats like "associated with malware C2". In code: Use the snippet above, then if response['score'] > 0.5, trigger a block command.
  2. Example 2: Bulk Domain Check For threat hunting, process a list of domains from a CSV: First, create a config file with {"ioc_list": ["example.com", "malicious.site"], "type": "domain"}, then run openclaw ioc-analysis --config domains.json --output report.csv. In a script, loop through the list via API calls and aggregate results for reporting.

Graph Relationships

  • Related to: threat-detection (shares IOC data for enhanced alerting)
  • Connected via: blue-team cluster (collaborates on incident response workflows)
  • Links to: red-team skills (for simulation and testing of IOC detection)
  • Dependencies: Requires access to external feeds like VirusTotal or AlienVault for enrichment

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.63%
按下载量换算45

Claude

30.79%
按下载量换算38

Cursor

19.09%
按下载量换算24

Gemini CLI

9.3%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills