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.
git clone --depth 1 https://github.com/haojing8312/WorkClawWrote 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/commands/haojing8312/workclaw/agents)<a href="https://agentmods.dev/commands/haojing8312/workclaw/agents"><img src="https://agentmods.dev/badge/commands/haojing8312/workclaw/agents/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/commands/haojing8312/workclaw/agents"><img src="https://agentmods.dev/badge/commands/haojing8312/workclaw/agents.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.00000 | $0.00996 |
| Opus 5.5 | $0.00000 | $0.00398 |
| Sonnet 5.5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
AGENTS 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Commands AGENTS.md
Scope
- This file applies to
apps/runtime/src-tauri/src/commands/. - Follow the closer rules here when editing command modules or adding new command-adjacent submodules.
Goal
- Keep Tauri command files as entrypoints, not as long-term homes for business logic, SQL, or provider protocols.
What Belongs In Root Command Files
- Tauri command function signatures
- command input parsing
- response shaping for the frontend contract
- obvious orchestration handoff to
service,repo,gateway, or sibling helper modules - small compatibility glue that must stay visible at the entrypoint
What Should Move Out
- long SQL blocks
- branching business policy
- normalization and validation flows shared by multiple commands
- external platform protocol handling
- large helper type clusters once they crowd out the command entrypoint
Preferred Submodules
<domain>/service.rs: business rules and orchestration<domain>/repo.rs: SQLite reads and writes<domain>/gateway.rsoradapter.rs: external integration logic<domain>/types.rs: internal DTOs and helper types
Use these as defaults, not dogma. Explain deviations before editing.
Reference Split
-
employee_agentsis the current reference split for giant Rust command files. -
Before designing a new command split, inspect:
src/commands/employee_agents.rssrc/commands/employee_agents/types.rssrc/commands/employee_agents/group_management.rssrc/commands/employee_agents/group_run_entry.rssrc/commands/employee_agents/memory_commands.rssrc/commands/employee_agents/tauri_commands.rs
-
Reuse that pattern of:
- thin root command file
- focused child modules by use case or responsibility
- explicit
service/repo/ command-helper boundaries - no giant replacement child file without a clear concern boundary
-
openclaw_pluginsis the current reference split for giant plugin or integration command files. -
Before designing a split for a command that mixes runtime state, setup, installation, and external host probing, inspect:
src/commands/openclaw_plugins.rssrc/commands/openclaw_plugins/tauri_commands.rssrc/commands/openclaw_plugins/runtime_service.rssrc/commands/openclaw_plugins/settings_service.rssrc/commands/openclaw_plugins/setup_service.rssrc/commands/openclaw_plugins/install_repo.rssrc/commands/openclaw_plugins/install_service.rssrc/commands/openclaw_plugins/plugin_host_service.rssrc/commands/openclaw_plugins/installer_session.rssrc/commands/openclaw_plugins/tests.rs
-
Reuse that pattern of:
- thin root command file
- command wrappers separated from setup, runtime, install, and host probing concerns
- explicit
service/repo/ command-helper boundaries - tests moved out of the root file once the root starts crowding out entrypoint logic
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.
- 1mo ago First seen · 88 lines · 0 tokens per session scan A de8bb86ef121
AGENTS is a command published in the GitHub repository haojing8312/WorkClaw (141 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 996 tokens. 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 commands, from other repositories
cargo-metadata
Command "cargo-metadata" from olorehq/olore, covering cargo-metadata(1), name, synopsis, description and output format.
mutation-test
Uses cargo-mutants to run mutation tests and verify test quality.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
cargo-build
Command "cargo-build" from olorehq/olore, covering cargo-build(1), name, synopsis, description and options.
cargo-check
Command "cargo-check" from olorehq/olore, covering cargo-check(1), name, synopsis, description and options.
cargo
Command "cargo" from olorehq/olore, covering cargo(1), name, synopsis, description and commands.