常驻用量

抄作业 / 做成了什么 / Grok Bot

grok-bot-intrusion-detection-team — 8-agent Windows IDS

标题与摘要为原文,未翻译。

做了什么
Eight-agent Grok Bot team that watches a Windows PC for intrusion signals, reports daily deltas, and only remediates after owner approval.
场景
周报 / 简报 盯 PR / 仓库 调研监控 写代码上线
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体有
  • 步骤 / 章节有
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

— 表示来源没有给出,本站不补写。

来源原文摘录
A team of eight Grok Bot agents that watches a Windows PC for signs of intrusion, reports only what changed each day, and fixes problems only after the owner approves each fix.
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

摘自项目 README,照录原文,未翻译。

效果截图
项目 README 图片
图片来自项目 README
来源里的步骤 / 要点
  1. Eight agents with clear roles. A team lead plus specialists for processes, network, persistence, logs, file integrity, the AI-agent layer, and deception.
  2. Baseline first, then changes only. Each specialist takes a full baseline of its area once. After that, it reports only what changed, so the daily summary stay…
  3. One daily sweep. Every day at a time the owner picks (9:27 AM ET, weekends included, on the original PC), each specialist checks for changes in turn, and the
  4. Incidents, not noise. When several specialists see parts of the same problem, the IDS Commander combines them into a single incident and sends targeted follow…
  5. A fix command with every finding. Each finding comes with the exact removal or response command. The specialist that found it never runs that command itself.
  6. AI agent protection. The AI Agent Monitor checks the agents on the PC itself: MCP server configs, rules files, hidden prompt injection, extensions, and AI key…
  7. Built-in tripwires. The Decoy Monitor plants harmless decoys that no legitimate user would open, so any touch is a high-confidence sign of an intruder.
  8. You stay in control. No fix and no decoy goes onto the PC until the owner approves it.

照录来源原文,未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制
  1. 打开仓库:github.com/ritvikindupuri/grok-bot-intrusion-detection-team ↗
  2. 读 README,把仓库链接发给你的 Bot,让它按 README 复现
  3. 先在小范围跑通,再加 routine
风险与限制
  • 定时运行会持续消耗额度:频率从低开始,跑稳再加
  • 多个 Bot 并行:额度按 Bot 数叠加,先合并职责相近的 Bot
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下