workdsh: Instructions file for Codex

AGENTS.md

workdsh AGENTS.md is an instructions file for Codex, OpenCode from techflag/workdsh. It costs 1,224 tokens per session, scanned A, original, MIT.

Repository instructions for the workdsh desktop project. They document its setup, build, tests, type checks, and checks needed when maintaining two desktop variants.

In plain words
What is it for?
Use them when installing, building, testing, type-checking, or validating shared changes in the workdsh desktop codebase.
Why use it?
They prevent agents from using the wrong runtime, package commands, or variant workflow when changing the repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is techflag/workdsh's own configuration. It tells Codex and OpenCode how to work on workdsh itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything workdsh configures →

Reuse

Borrowing it

Nothing to install: this file belongs to techflag/workdsh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/techflag/workdsh/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/techflag/workdsh

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 workdsh AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/techflag/workdsh/agents-md/github.svg)](https://agentmods.dev/instructions/techflag/workdsh/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/techflag/workdsh/agents-md"><img src="https://agentmods.dev/badge/instructions/techflag/workdsh/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.

agentmods 80×15 button for workdsh AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/techflag/workdsh/agents-md"><img src="https://agentmods.dev/badge/instructions/techflag/workdsh/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,224 This file is loaded in full into every session.
When invoked 1,224 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01224 $0.01224
Opus 5.5 $0.00490 $0.00490
Sonnet 5.5 $0.00245 $0.00245
Haiku 4.5 $0.00122 $0.00122

Measured 11d ago against content hash 876803c77afd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workdsh 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 11d 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 · 51 lines

How it starts

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

DSH Desktop repository rules

This repository owns WorkDSH Web and Desktop. Desktop and Web consume the same exact official DSH published package version. Desktop binary dependencies and command-management helpers are extracted from checksum-locked official release installers.

Git branch and release policy

  • Keep exactly one long-lived product branch: the GitHub default branch, currently main. Do not maintain main and master as parallel product or release lines.
  • Development and migration branches are temporary. Bring every accepted change back to the default branch through a reviewed pull request; verify required checks and that the intended commits are present there before treating the work as delivered.
  • Create Desktop release tags and publish product artifacts only from commits reachable from the default branch. A successful build on a temporary branch is validation, not a release.
  • After a temporary branch has been merged and its changes verified on the default branch, delete that temporary branch. Retain an unmerged branch only while its work is still under review; do not delete unique history.
  • If the default branch is renamed, update GitHub settings, CI, website deployment, release triggers, and documentation together before removing the old branch.

Prerequisites and setup

  • Use Node.js ^22.19.0 or >=24.0.0 and the root Yarn 4.18.0 release through Corepack.
  • Install root dependencies with corepack yarn install --immutable.

Build, run, and verify

  • Start the desktop development workflow with corepack yarn dev.
  • Build the desktop package with corepack yarn build.
  • Run unit tests with corepack yarn test.
  • Run type checking with corepack yarn typecheck.
  • Run the complete headless gate with corepack yarn check.
  • apps/desktop/ is the only Desktop source and release workspace. Do not reintroduce a copied Beta package; optional release channels must build from this same source and pinned DSH version.
  • The official release version locked in upstream.json is the single DSH version for the packaged WorkDSH Profile. Desktop source is an Electron carrier without direct DSH dependencies. A DSH upgrade is incomplete until corepack yarn check:desktop-dsh-alignment, the Desktop checks, and a packaged-runtime check pass. Default to the newest official stable DSH release after compatibility validation; use a pre-release only by explicit product decision. Do not tag a Desktop release while the version gate fails. The carrier must contain no second DSH installation.
  • apps/web/ owns Web launch, deployment and verification. Root packages/ owns shared WorkDSH feature packages, and root profiles/ owns composition. Its package manifests must declare the same exact DSH version as upstream.json; run corepack yarn check:web-dsh-alignment when either side changes. The Web workspace remains self-contained and does not import or modify the official source tree.

Read the full file on GitHub · 51 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. 11d ago Changed · +12 lines · +320 tokens per session 876803c77afd
  2. 19d ago Changed · -75 lines · -2,878 tokens per session bc8b37e7c409
  3. 21d ago Changed · +82 lines · +3,145 tokens per session 71ee7ea6f3a3
  4. 22d ago First seen · 32 lines · 637 tokens per session scan A 2f5957f5d11e

Subscribe to this mod's changes

workdsh AGENTS.md is an instructions file published in the GitHub repository techflag/workdsh (227 stars, last pushed 7d ago), licensed MIT. It adds 1,224 tokens to every session, about $0.0049 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-09-23.

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 · 9,649 tokens

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.

vercel/next.js · 7,257 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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.

deepseek-ai/deepseek-harness · 4,159 tokens

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

microsoft/vscode · 2,731 tokens