agentmods.dev

dglabs-deepclaw AGENTS.md

A repository guide for the OpenClaw codebase, covering its folders, extensions, documentation, tests, installers, and contribution rules.

In plain words
What is it for?
Use it when modifying OpenClaw source code, extensions, tests, Mintlify documentation, Chinese documentation, installers, or related virtual-machine operations.
Why use it?
It gives a coding agent the project’s layout and rules so changes are made in the expected places and dependencies are configured correctly.

Instructions file for CodexOpenCode

23 3mo ago B scan 4,591 tokens copy · 95% MIT
View the source file deepgram/dglabs-deepclaw
Install

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.

agentmods
npx agentmods add instructions/deepgram/dglabs-deepclaw/agents-md
Clone the repo
git clone --depth 1 https://github.com/deepgram/dglabs-deepclaw

Made for: Codex, OpenCode.

Per session 4,591 This file is loaded in full into every session.
When invoked 4,591 The same file — it is already loaded in full.
Security scan B 1 finding. Scan, not verified.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.04591 $0.04591
Opus 5 $0.02295 $0.02295
Sonnet 5 $0.00918 $0.00918
Haiku 4.5 $0.00459 $0.00459

Measured 2d ago against content hash 540857dec425, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

dglabs-deepclaw 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Update: `sudo npm i -g openclaw@latest` (global install needs root on `/usr/lib/node_modules`).
Origin

This is a copy

95% identical to openclawvn AGENTS.md — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

  • Source code: src/ (CLI wiring in src/cli, commands in src/commands, web provider in src/provider-web.ts, infra in src/infra, media pipeline in src/media).
  • Tests: colocated *.test.ts.
  • Docs: docs/ (images, queue, Pi config). Built output lives in dist/.
  • Plugins/extensions: live under extensions/* (workspace packages). Keep plugin-only deps in the extension package.json; do not add them to the root package.json unless core uses them.
  • Plugins: install runs npm install --omit=dev in plugin dir; runtime deps must live in dependencies. Avoid workspace:* in dependencies (npm install breaks); put openclaw in devDependencies or peerDependencies instead (runtime resolves openclaw/plugin-sdk via jiti alias).
  • Installers served from https://openclaw.ai/*: live in the sibling repo ../openclaw.ai (public/install.sh, public/install-cli.sh, public/install.ps1).
  • Messaging channels: always consider all built-in + extension channels when refactoring shared logic (routing, allowlists, pairing, command gating, onboarding, docs).
    • Core channel docs: docs/channels/
    • Core channel code: src/telegram, src/discord, src/slack, src/signal, src/imessage, src/web (WhatsApp web), src/channels, src/routing
    • Extensions (channel plugins): extensions/* (e.g. extensions/msteams, extensions/matrix, extensions/zalo, extensions/zalouser, extensions/voice-call)
  • When adding channels/extensions/apps/docs, review .github/labeler.yml for label coverage.

Docs Linking (Mintlify)

  • Docs are hosted on Mintlify (docs.openclaw.ai).
  • Internal doc links in docs/**/*.md: root-relative, no .md/.mdx (example: [Config](/configuration)).
  • Section cross-references: use anchors on root-relative paths (example: [Hooks](/configuration#hooks)).
  • Doc headings and anchors: avoid em dashes and apostrophes in headings because they break Mintlify anchor links.
  • When Peter asks for links, reply with full https://docs.openclaw.ai/... URLs (not root-relative).
  • When you touch docs, end the reply with the https://docs.openclaw.ai/... URLs you referenced.
  • README (GitHub): keep absolute docs URLs (https://docs.openclaw.ai/...) so links work on GitHub.
  • Docs content must be generic: no personal device names/hostnames/paths; use placeholders like user@gateway-host and “gateway host”.

Read the full file on GitHub · 190 lines

Changes

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.

  1. 2d ago First seen · 190 lines · 4,591 tokens per session scan B 540857dec425

Subscribe to this mod's changes

dglabs-deepclaw AGENTS.md is an instructions file published in the GitHub repository deepgram/dglabs-deepclaw (23 stars, last pushed 3mo ago), licensed MIT. It adds 4,591 tokens to every session, about $0.0230 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 95% identical to openclawvn AGENTS.md, differing in 17 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens