acryl AGENTS.md

Repository instructions for a desktop product built around a pinned copy of DeepSeek Harness. They cover the required Node.js and pnpm setup, isolated development mode, builds, type checks, tests, and verification.

In plain words
What is it for?
Use them when setting up the repository, running an isolated desktop instance, checking or testing changes, building the package, or updating the upstream submodule.
Why use it?
They prevent developers from using the installed app's data accidentally and provide the approved commands for checking both the desktop wrapper and its upstream code.

Instructions file for CodexOpenCode

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/acryldev/acryl/agents-md
Clone the repo
git clone --depth 1 https://github.com/acryldev/acryl

Made for: Codex, OpenCode.

Per session 1,543 This file is loaded in full into every session.
When invoked 1,543 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.01543 $0.01543
Opus 5 $0.00772 $0.00772
Sonnet 5 $0.00309 $0.00309
Haiku 4.5 $0.00154 $0.00154

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

Security

Grade A, and why

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

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 · 102 lines

How it starts

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

DSH Desktop repository rules

This repository owns the desktop product around an unmodified DeepSeek Harness checkout.

Prerequisites and setup

  • Use Node.js ^22.19.0 or >=24.0.0 and the root PNPM 11.7.0 release through Corepack.
  • Initialize the pinned upstream checkout with git submodule update --init --recursive.
  • Install root dependencies with corepack pnpm install --frozen-lockfile.

Build, run, and verify

  • Start the isolated local Desktop (own ~/.dsh-acryl home, advanced mode, Development Canvas) with corepack pnpm run dev or corepack pnpm run local.

  • Use corepack pnpm run dev:shared only when you intentionally want the installed app's ~/.dsh home.

  • Fast headless loop: corepack pnpm run typecheck, corepack pnpm run test, or both via corepack pnpm run verify.

  • Typecheck, test, then isolated GUI: corepack pnpm run lifecycle.

  • Build the desktop package with corepack pnpm run build.

  • Run the complete headless gate with corepack pnpm run check.

  • Run upstream operations through the root scripts, such as corepack pnpm run upstream:build.

  • deepseek-harness/ is a pinned upstream Git submodule. Never edit files inside it from a desktop feature branch.

  • acryl-desktop/ owns the Cordis Host and Client faces, Electron bootstrap, packaging, and release tests.

  • dsh-community-fabric/ owns the community interoperability RFC. Until schemas and a reviewed reference adapter exist, it remains a private documentation scaffold and must not declare loadable DSH or package entry points.

  • dsh-community-market/ is an implemented private Host/Client package. It is an optional Desktop Market provider, disabled by default, and must continue to use ordinary DSH/Cordis, profile, and Desktop service contracts rather than a parallel plugin runtime.

  • The outer repository and all owned packages use the root PNPM release with node-linker=isolated.

  • The upstream submodule keeps its own PNPM workspace. Run upstream commands through the root upstream:* scripts, which enter the submodule before invoking its pinned Corepack release.

  • Compatibility mode must run the upstream default client without overrides. Advanced presentation belongs to desktop-owned client plugins and may replace documented slots or services through profile composition.

  • Keep graphical application launch explicit. Builds, typechecks, unit tests, and Loader smokes must remain headless-safe.

  • During the current small-team rapid-development phase, work directly on main unless the user explicitly requests a branch or pull request. Do not create routine PRs.

  • Commit every important coherent change promptly so regressions can be reverted to a precise checkpoint. Prefer several focused commits over rare large snapshots.

  • Record every important product, architecture, workflow, or operational evolution in docs/DEVELOPMENT-LOG.md. Commit the implementation first, then add its full canonical commit hash and human-readable explanation to the log in a separate documentation checkpoint. Update logged hashes after any history rewrite or squash.

  • Commit before major changes of direction and keep the submodule pin update separate from desktop behavior changes.

  • Keep the repository topology and package-manager split consistent with the owning Agent Note.

Read the full file on GitHub · 102 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 · 102 lines · 1,543 tokens per session scan A b4f23988258f

Subscribe to this mod's changes

acryl AGENTS.md is an instructions file published in the GitHub repository acryldev/acryl (220 stars, last pushed 2d ago), licensed MIT. It adds 1,543 tokens to every session, about $0.0077 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.