decepticon

GitHub

Decepticon CLI操作技能,用于启动、恢复、检查安全参与任务及本地Blue Cell。涵盖版本检查、交互式终端交互、状态诊断、日志查看及报告生成,强调正确命令使用与凭据安全。

skills/decepticon/SKILL.md BitterSecurity/Decepticon

触发场景

用户请求设置或运行 Decepticon 安全平台 用户需要诊断或检查 Decepticon 参与任务状态 用户希望恢复或继续之前的 Decepticon 会话 用户请求查看 Decepticon 服务状态或日志

安装

npx skills add BitterSecurity/Decepticon --skill decepticon -g -y
更多选项

不安装直接使用

npx skills use BitterSecurity/Decepticon@decepticon

指定 Agent (Claude Code)

npx skills add BitterSecurity/Decepticon --skill decepticon -a claude-code -g -y

安装 repo 全部 skill

npx skills add BitterSecurity/Decepticon --all -g -y

预览 repo 内 skill

npx skills add BitterSecurity/Decepticon --list

SKILL.md

Frontmatter
{
    "name": "decepticon",
    "license": "Apache-2.0",
    "metadata": {
        "homepage": "https:\/\/github.com\/BitterSecurity\/Decepticon"
    },
    "description": "Operate the Decepticon security platform through its CLI when the user asks to set up, diagnose, run, resume, or inspect a Decepticon engagement or local Blue Cell. Use for Decepticon operations, not general security advice or standalone scanner commands."
}

Decepticon CLI

Wrap the installed decepticon command. Check its version and help before choosing commands; installed releases may differ from repository main.

decepticon --version
decepticon --help
decepticon status --json
decepticon doctor --json

If the command is missing, use the project's installation guide. Do not install a similarly named Python package as a launcher replacement. For first-time configuration use decepticon onboard; it needs an interactive terminal and provider input. Never include credentials in a report.

Run and resume

decepticon start starts services and opens an interactive terminal UI. Run it in a persistent PTY when the host agent supports terminal interaction. Read the screen, enter the requested input, and inspect the resulting screen before sending another action. Without interactive terminal access, hand the exact command to the operator. Do not claim that a background shell launch completed an engagement.

decepticon start
decepticon --resume             # choose a saved session
decepticon --resume=<thread-id> # resume a known session
decepticon --continue           # continue the latest session

New engagements prompt for a name, in-scope targets and exclusions, then show the normalized scope for review. Optional discovery suggestions are included only when selected. Use the user's authorization; ask only for missing scope information. Saved scopes are retained. There is no separate /mode red approve command or approval marker. Plan is optional. Enter /help inside the terminal for commands supported by that running version.

Slash commands such as /status, /sessions, /mode, /blue, /web, and /export are terminal input, not shell subcommands. Do not invent shell forms like decepticon scan, decepticon blue up, or decepticon start --target. See examples.md for terminal, service, and result workflows.

Inspect and report

Use decepticon status --json for service state and decepticon doctor --json for diagnostics. Use decepticon engagements to list local workspaces and decepticon logs --engagement <name-or-thread-id> --limit 20 to replay recent conversation messages. decepticon logs langgraph follows service logs; bound the observation with the host terminal timeout or interrupt it after the needed sample. Consult logs --help first. A running container does not establish engagement progress or completion.

Read the conversation and actual workspace findings/FIND-*.md and report/ artifacts when available. Report observed state, evidence paths, verification status, and remaining work. Missing artifacts do not establish a clean result. Exiting the UI leaves services running; use decepticon stop when the user requests stack shutdown. update, onboard --reset, and remove change the installation: use them only when the requested operation calls for them.

decepticon cancel <name-or-thread-id> requests cancellation of an active agent run and leaves services running. Use it when the user requests a run stop, then inspect the transcript to report the observed outcome.

Optional MCP integration

The CLI workflow does not require MCP. If the user already has Decepticon MCP tools and asks for programmatic background control or observation, use reference.md for their arguments, cursors, workspace constraints, and findings limitations. Registering MCP is documented in the integration guide. Do not run decepticon mcp serve as a one-shot shell query; it is a persistent stdio server. MCP tools and skill retrieval do not grant target authorization.

版本历史

  • cd252a5 当前 2026-11-03 10:15

同 Skill 集合

integrations/agent-skills/decepticon/SKILL.md
packages/decepticon/decepticon/skills/benchmark/SKILL.md

元信息

文件数
0
版本
cd252a5
Hash
cd697b40
收录时间
2026-11-03 10:15

首页 - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-21 17:42
浙ICP备14020137号-1