DingTalk Workspace CLI is a cross-platform command-line tool that brings DingTalk’s product capabilities into one interface. It serves human users and AI agents working with DingTalk enterprise data, with administrator authorization required. Its catalogue add-ons provide agent skills for using the CLI’s product areas.
Borrowing it
Nothing to install: this file belongs to DingTalk-Real-AI/dingtalk-workspace-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DingTalk-Real-AI/dingtalk-workspace-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/DingTalk-Real-AI/dingtalk-workspace-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md)<a href="https://agentmods.dev/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.09631 | $0.09631 |
| Opus 5.5 | $0.03852 | $0.03852 |
| Sonnet 5.5 | $0.01926 | $0.01926 |
| Haiku 4.5 | $0.00963 | $0.00963 |
Grade A, and why
dingtalk-workspace-cli AGENTS.md scanned grade A with 0 findings 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 16d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 701 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Agent Guide
This file applies to the entire repository. Keep changes scoped, preserve
unrelated work, and use gofmt for every modified Go file.
Build and test
- Build:
make build(wrapsscripts/dev/build.sh→go build -o dws ./cmd; barego build ./cmdfails because output namecmdcollides with the directory) - Full test suite:
DWS_PACKAGE_VERSION=0.0.0-test go test ./... - Param aliases generate:
go generate ./internal/cli(entry point:internal/cli/gen.go; Catalog is not generated) - Optional diagnostic MCP dump (not a Schema pin):
make fetch-mcp-metadata(requiresdws auth login; writes underartifacts/) - Check generated drift + assembly determinism:
./scripts/policy/check-generated-drift.sh - Check the Schema contract:
./scripts/policy/check-schema-catalog.sh - Coverage-gate test naming: tests that carry coverage for the macOS platform
gate must be named
TestCrossPlatformCoverage*(orTestAllShortcuts*);scripts/policy/run-platform-coverage-gate.shonly selects those prefixes, so a covering test with any other name silently leaves its target uncovered. - Package-var injection seams (e.g.
pipelineBuildEffectiveRegistry): swap them in tests only viatestseam.Swap(t, &seam, stub)frominternal/testseam— it restores the previous value throught.Cleanupstructurally. Like the manual pattern it replaces, Swap mutates global state and is not safe fort.Paralleltests. - Cross-package test helpers (e.g.
StoreProductDeclRawForTest) live in per-packagefortest.gofiles, never scattered through production files; theForTestsuffix is the boundary and production code must not call them.
Schema Catalog delivery is 声明即 Catalog: production assembles via
RegisterSchemaSourceRoot → ResolveSchemaBuild (factory registered in
internal/app). Schema identity is not produced at compile or release
time; shipping binaries do not embed binary-pinned cache digests. On
supported platforms (darwin/linux/windows amd64/arm64) production enables the
persistent cache: install or the first schema-consuming path generates
identity from this binary's live declarations, writes authenticated disk
shards, and later processes load that local identity then verify digests
before reading protobuf. A missing sidecar generates then uses the cache;
it is not a permanent live-only mode. Plugins that change the command
surface delegate cache assembly and repair to an isolated child process
using the pristine environment captured before plugin registration; the parent
process does not assemble cache directly, while reading, repairing, and
publishing authenticated cache remains fully active. Plugin commands never
enter the Schema surface, cached or live. Tests may also inject identity via
RegisterSchemaCacheOptions.
See docs/rfc-schema-runtime-cache.md for the single RFC covering the
local-identity shipping model, complete-tree performance contract, cache
delivery; no sibling plan/design/performance pages are kept. Telemetry
delivery is the detached background-process model (see
.changes/clitrack-detached-reporting.md), not the retired in-process
NoFlushWait CLI default.
There is no
cmd_schema_catalog //go:generate delivery step. dws schema -f json remains
the wire projection. cmd_schema_catalog produces CI/local dumps only;
internal/cli/schema_catalog/, internal/cli/schema_meta_index.gob, and
internal/cli/schema_meta_index.json must not be committed. schema_agent_metadata/ is retired: if that directory
(or schema_agent_metadata_audit.json) is present, policy fails.
Command identity is no longer a file input: it is collected from
ContractFinal.Identity on the live Cobra leaves
(internal/cli/schema_identity_collect.go → BuildEffectiveCommandRegistry).
The reviewed schema_command_registry/ was retired together with that
switchover and must not reappear; identity changes happen by editing the leaf
declaration. The remaining reviewed inputs under internal/cli (see Agent
Schema contract) keep separate authorities — do not merge them with
param_concepts.json or promote any of them into Catalog declaration.
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.
- 16d ago Changed · +11 lines · +257 tokens per session 640af0d442a2
- 1mo ago Changed · +2 lines · +22 tokens per session c5699eb6aad5
- 1mo ago Changed · +70 lines · +1,423 tokens per session 048cd42f7bdc
- 1mo ago First seen · 618 lines · 7,929 tokens per session scan A ff456cca4a0c
dingtalk-workspace-cli AGENTS.md is an instructions file published in the GitHub repository DingTalk-Real-AI/dingtalk-workspace-cli (3,788 stars, last pushed 2d ago), licensed Apache-2.0. It adds 9,631 tokens to every session, about $0.0385 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.