dingtalk-workspace-cli AGENTS.md

dingtalk-workspace-cli AGENTS.md is an instructions file for Codex, OpenCode from DingTalk-Real-AI/dingtalk-workspace-cli. It costs 7,929 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for a Go command-line tool, including how to build, test, generate command aliases, and check its schemas.

In plain words
What is it for?
Use them when changing the DingTalk workspace CLI, especially its commands, flags, help text, generated files, schemas, or tests.
Why use it?
They give coding agents the project’s required checks and conventions, avoiding incorrect build commands, missed generated changes, and incomplete coverage tests.

Instructions file for CodexOpenCode

About the project

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.

DingTalk-Real-AI/dingtalk-workspace-cli · 2,861 stars · on GitHub

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/dingtalk-real-ai/dingtalk-workspace-cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli

Made for: Codex, OpenCode.

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

agentmods badge for dingtalk-workspace-cli AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md.svg)](https://agentmods.dev/instructions/dingtalk-real-ai/dingtalk-workspace-cli/agents-md)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 7,929 This file is loaded in full into every session.
When invoked 7,929 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.07929 $0.07929
Opus 5 $0.03964 $0.03964
Sonnet 5 $0.01586 $0.01586
Haiku 4.5 $0.00793 $0.00793

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

Security

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 5d 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.

AGENTS.md · 618 lines

How it starts

The opening of the file, as written. The whole thing — 618 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 (wraps scripts/dev/build.shgo build -o dws ./cmd; bare go build ./cmd fails because output name cmd collides 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 (requires dws auth login; writes under artifacts/)
  • 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* (or TestAllShortcuts*); scripts/policy/run-platform-coverage-gate.sh only 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 via testseam.Swap(t, &seam, stub) from internal/testseam — it restores the previous value through t.Cleanup structurally. Like the manual pattern it replaces, Swap mutates global state and is not safe for t.Parallel tests.
  • Cross-package test helpers (e.g. StoreProductDeclRawForTest) live in per-package fortest.go files, never scattered through production files; the ForTest suffix is the boundary and production code must not call them.

Schema Catalog delivery is 声明即 Catalog: production assembles via RegisterSchemaSourceRootResolveSchemaBuild (factory registered in internal/app). 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.goBuildEffectiveCommandRegistry). 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.

Read the full file on GitHub · 618 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. 5d ago First seen · 618 lines · 7,929 tokens per session scan A ff456cca4a0c

Subscribe to this mod's changes

dingtalk-workspace-cli AGENTS.md is an instructions file published in the GitHub repository DingTalk-Real-AI/dingtalk-workspace-cli (2,861 stars, last pushed yesterday), licensed Apache-2.0. It adds 7,929 tokens to every session, about $0.0396 per session on Opus 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.