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 agentmods add instructions/xxxxxccc/devops-bot/agents-mdgit clone --depth 1 https://github.com/xxxxxccc/devops-botWhat 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 | $0.01134 | $0.01134 |
| Opus 5 | $0.00567 | $0.00567 |
| Sonnet 5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade B, and why
devops-bot AGENTS.md scanned grade B 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 2d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Shell tool blocks dangerous commands (`rm -rf /`, `sudo`, `shutdown`, etc.) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Bot
Chat-driven AI coding agent. Users communicate via IM group chat (Feishu or Slack), a two-layer AI system classifies intent and executes code changes automatically. Supports multiple AI providers (Anthropic, OpenAI, OpenAI-compatible).
Commands
| Task | Command |
|---|---|
| Dev (hot reload) | pnpm dev |
| Build | pnpm build |
| Start | pnpm start |
| Lint + Format check | pnpm check |
| Lint only | pnpm lint |
| Format (write) | pnpm format |
Always run pnpm check before committing.
Critical Conventions
- ESM + NodeNext: All imports must use
.jsextension (e.g.,import { foo } from './bar.js') - Node.js builtins: Use
node:protocol (e.g.,import { readFile } from 'node:fs/promises') - Biome for formatting and linting — not ESLint, not Prettier
- Single quotes, no semicolons, trailing commas (enforced by Biome)
- pnpm as package manager — do not use npm or yarn
- No new dependencies without justification; prefer Node.js builtins
Project Context
- Supports multi-project mode — projects added via chat (
add_projectintent), auto-cloned to~/.devops-bot/repos/ - Supports workspace mode — register a workspace meta-repo (
add_workspaceintent) withworkspace.jsonmanifest; dispatcher AI sees all sub-projects and clones on demand viatargetGitUrl - Falls back to single-project mode if
TARGET_PROJECT_PATHis set - IM bot (Feishu or Slack) is the primary user interface — there is no web frontend
- Two AI layers: fast model (dispatcher) and powerful model (task executor) — provider-agnostic
- Three-tier task execution:
execute_task(low risk, immediate),propose_task(medium risk, needs approval via Issue AI synthesis),create_issue(high risk, discussion only) - PR Review: AI-powered code review via
review_printent, self-review after task completion (with auto-fix loop — up to 2 rounds), or polling/webhook triggers; Memory namespace isolation (taskvsreview) with selective cross-injection; full PR discussion context (issue comments + review summaries) injected into review and fix prompts - Issue AI: Independent AI layer that reads full issue context (body + comments) and synthesizes actionable tasks; also scans external issues with configured labels; in workspace mode, uses two-phase cross-repo triage (quality gate + routing to sub-projects, with sub-issue creation)
- GitHub App authentication for GitHub operations (PRs, Issues, git push); PAT fallback supported
- Skills stored at workspace level (
~/.devops-bot/skills/), shared across all projects - Memory persists in
data/memory/using SQLite (primary) + JSONL exports (AI browsing); features semantic dedup (LLM-driven ADD/UPDATE/NOOP/DELETE decision cycle), change audit trail (memory_historytable), periodic pruning of stale memories, and per-project custom extraction prompts via.devops-bot.json - Configuration lives in
.env.local(never committed)
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.
- 2d ago First seen · 62 lines · 1,134 tokens per session scan B 2953f5084035
devops-bot AGENTS.md is an instructions file published in the GitHub repository xxxxxccc/devops-bot (47 stars, last pushed 4mo ago), licensed MIT. It adds 1,134 tokens to every session, about $0.0057 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
chat AGENTS.md
Instructions for vercel/chat, covering agents.md, commands, per-package, monorepo layout and architecture.
agentconnect CLAUDE.md
Instructions for agentconnect-md/agentconnect, covering claude.md, what this is, monorepo (pnpm workspace, packages/), platform modules and comment style.
personal-agent-template AGENTS.md
Instructions for vercel-labs/personal-agent-template, covering personal agent template, quick reference, structure, documentation and eve framework.
openlark AGENTS.md
Instructions for foxzool/openlark, covering openlark knowledge base, structure, where to look, conventions and 模块组织.
macro CLAUDE.md
Claude Code instructions for macro-inc/macro, covering claude.md, architecture overview, key services, data storage and macrodb schema changes.
larksnap CLAUDE.md
Instructions for AmbroseX/larksnap, covering 基本约定, plan 文件管理, 开发规范, 根据场景动态调整顺序 and 文档写入.