360 Secure SkillHub
360 安全技能中心

Axodus Trading Integration

核心功能为安全集成hummingbot或MCP Axodus Trading交易基础设施,默认纸盘执行模式,提供全链路审计日志与严格风险管控。适用于新增/更新hummingbot连接器、对接MCP执行接口、搭建行情、订单路由或策略执行模块。输入需指定集成目标,可选配置模式、支持市场、风控规则等;输出含集成摘要、配置约定、验证手册,遵循默认纸盘、不存明文密钥等安全规则。

mzfshark
mzfshark
热度 43.56
最近更新 2026-05-11 17:45:41
分类:开发依赖:代码执行 / MCP 服务 / 第三方 API / 读写文件应用场景:API 集成 / 代码生成 / 数据处理 / DevOps

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add axodus-trading-integration
Metadata
name
trading-integration
description
Integrate trading infrastructure (hummingbot/MCP) with paper-first mode and audit logs.
metadata
{"author":"RedHat Dev","version":"1.0.0","owner":"RedHat Dev Agent","category":"trading"}

SKILL: trading-integration

Purpose

Integrate trading infrastructure safely (hummingbot and/or MCP Axodus Trading) with paper-first execution, full logging/auditability, and strict risk gating.

When to Use

  • Adding or updating connectors for hummingbot.
  • Wiring execution to MCP Axodus Trading interfaces.
  • Building market data ingestion, order routing, or strategy execution surfaces.

Inputs

  • targets (required, string[]): e.g., ["hummingbot", "mcp-axodus-trading"]
  • mode (optional, enum: paper|live, default: paper)
  • markets (optional, string[]): symbols/venues to support.
  • risk_limits (optional, object): max risk per trade, max drawdown, exposure caps, kill-switch.
  • logging_requirements (optional, string[]): required audit events.

Steps

  1. Confirm non-negotiables:
    • no profit guarantees
    • paper mode default
    • full logs for signal/decision/execution/result
  2. Map integration points:
    • market data feeds
    • execution endpoints
    • capital allocation interface
  3. Implement configuration surfaces:
    • env/config references (no secrets in repo)
    • explicit mode flag for live
  4. Implement deterministic execution flow:
    • preflight checks (risk limits, connectivity)
    • order submission
    • order state tracking
    • post-trade recording
  5. Implement failure handling:
    • bounded retries
    • fallback to safe stop
    • kill-switch triggers on abnormal loss
  6. Validate in paper mode:
    • dry-run order lifecycle
    • audit logs produced
    • risk gating blocks unsafe actions

Validation

  • Live mode cannot run without an explicit flag and passing preflight checks.
  • All actions emit audit logs (no silent decisions).
  • Risk limits are enforced before order placement.
  • Secrets are not printed or committed.

Output

  • Integration summary (what’s wired)
  • Config contract (required env vars, mode flags)
  • Validation commands/runbook (paper test loop)

Safety Rules

  • Never enable live trading by default.
  • Never request or store exchange API keys in plaintext.
  • Never frame outcomes as guaranteed profit; treat as experimental systems with controlled risk.

Example

Paper-first integration:

  • targets: ["hummingbot"]
  • mode: paper
  • Output: runbook describing simulated order placement and expected audit log entries.