agentmods.dev

WorkClaw AGENTS.md

Project-specific instructions for WorkClaw, a desktop application with a React interface, a Rust backend, and a separate runtime process. They explain the main folders, local workflow skills, and release rules.

In plain words
What is it for?
Use them when working on the desktop app, Rust packages, sidecar integrations, provider or tool permissions, testing, or release preparation.
Why use it?
They tell a coding agent which guidance and checks apply before changing runtime behavior, permissions, tests, or release files. This helps keep changes aligned with the repository's process.

Instructions file for CodexOpenCode

140 3mo ago A scan 6,038 tokens original Apache-2.0
View the source file haojing8312/WorkClaw
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/haojing8312/workclaw/agents-md
Clone the repo
git clone --depth 1 https://github.com/haojing8312/WorkClaw

Made for: Codex, OpenCode.

Per session 6,038 This file is loaded in full into every session.
When invoked 6,038 The same file — it is already loaded in full.
Security scan A 1 finding. 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.06038 $0.06038
Opus 5 $0.03019 $0.03019
Sonnet 5 $0.01208 $0.01208
Haiku 4.5 $0.00604 $0.00604

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

Security

Grade A, and why

WorkClaw AGENTS.md scanned grade A 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -I http://localhost:5174
AGENTS.md · 248 lines

How it starts

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

AGENTS.md instructions for E:/code/yzpd/workclaw

Project Overview

  • apps/runtime/ contains the React desktop app shell, frontend flows, and UI tests.
  • apps/runtime/src-tauri/ contains the Tauri backend, desktop integrations, and Rust integration tests.
  • apps/runtime/sidecar/ contains the sidecar runtime, adapters, browser automation bridge, and sidecar tests.
  • packages/* contains shared Rust crates for routing, policy, models, executor, skill packaging, and runtime support.
  • Root package.json commands are the source of truth for local verification and release-sensitive checks.

Repo-Local Workflow Skills

  • $workclaw-implementation-strategy: Use before editing runtime behavior, routing, provider integration, tool permissions, sidecar bridge behavior, or vendor sync boundaries.
  • $workclaw-change-verification: Use when changes affect code, tests, builtin skill assets, or build/test behavior before claiming the work is complete.
  • $workclaw-release-readiness: Use when changes affect versioning, release documentation, installer branding, packaging outputs, or vendor release lanes before deciding a branch is safe to ship.
  • $workclaw-release-prep: Use before publishing to recommend the next version and draft bilingual Chinese + English release notes for confirmation.
  • $workclaw-release-publish: Use only after version and release notes are confirmed, to update release metadata, push the release tag, and generate local desktop artifacts.

Repo Hygiene Governance

  • Treat orphan files, dead code, stale docs, duplicate implementations, and temporary artifacts as a maintenance surface, not a one-off cleanup task.
  • Prefer repo hygiene review before deletion. Do not remove suspicious files or code only because they appear unused in one static signal.
  • Use pnpm review:repo-hygiene for non-blocking repo hygiene reporting when the task is cleanup-focused or when a large feature leaves likely follow-up debris.
  • Use focused repo hygiene subcommands when one narrow signal is enough:
    • pnpm review:repo-hygiene:deadcode
    • pnpm review:repo-hygiene:artifacts
    • pnpm review:repo-hygiene:drift
    • pnpm review:repo-hygiene:dup
    • pnpm review:repo-hygiene:loc
    • pnpm review:repo-hygiene:cycles
  • Use pnpm report:frontend-large-files when reviewing frontend file growth before split planning.
  • Treat duplicate implementations, oversized files, and import cycles as review-first governance signals. They should trigger triage and split plans, not blind deletion or mechanical rewrites.
  • Use workclaw-repo-hygiene-review to classify candidates and recommend the smallest safe cleanup batch before destructive edits.
  • Use workclaw-cleanup-execution only after review selected a cleanup batch and its reviewed action per file.
  • Cleanup changes still require workclaw-change-verification when code, tests, docs, or skill files change.
  • Treat generated, runtime-owned, dynamically discovered, or config-driven files as high-risk cleanup surfaces unless a rule explicitly marks them safe.

Read the full file on GitHub · 248 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. 3d ago First seen · 248 lines · 6,038 tokens per session scan A 8747bc328248

Subscribe to this mod's changes

WorkClaw AGENTS.md is an instructions file published in the GitHub repository haojing8312/WorkClaw (140 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 6,038 tokens to every session, about $0.0302 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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