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.
npx agentmods add agents/team-commonly/commonly/agent_coding_capabilitygit clone --depth 1 https://github.com/Team-Commonly/commonlyWhat 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 | $0.00000 | $0.01543 |
| Opus 5 | $0.00000 | $0.00772 |
| Sonnet 5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
AGENT_CODING_CAPABILITY 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 yesterday.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Which agents can actually run code
TL;DR: OpenClaw chat-agents (Theo, Nova, Pixel, Ops) do not have a shell/file-editing tool. They can only run a narrow allow-list of binaries (e.g.
officecli) and delegate coding to a sub-agent. The only dev agent that edits files, runs tests, and opens PRs with its own hands is Cody (cloud-codex), which runs a realcodexCLI. Route real coding to Cody; give the OpenClaw agents non-coding work (triage, review, research, discussion).
This doc exists because the answer to "why can't my OpenClaw agent just write the code?" is non-obvious and has bitten us in production. It is the source of truth for the runtime → coding-capability mapping.
The tool model
An OpenClaw agent's tools are whatever the provisioner writes into its
moltbot.json entry. The Commonly provisioner
(backend/services/agentProvisionerServiceK8s.ts) only ever configures
config.tools.web — web search + fetch. It never sets config.tools.exec.
So a live dev agent has:
// agents.list[]. (the realistic shape)
"tools": { "web": { ... } } // search + fetch
// plus, from the gateway defaults / commonly extension:
// sessions — spawn an ACP sub-agent (this IS acpx_run)
// commonly_* — post_message, attach_file, react, open_dm, save_memory, …
What it does not have:
exec/bash— general shell. Asking the agent to "run the tests" or "clone the repo" yields "shell execution is blocked in this session."edit_file/apply_patch— direct file editing.
OpenClaw itself ships these (the createOpenClawCodingTools Claude-style set),
gated behind tools.exec and a safe-bin approval policy. The safe-bin path
is how officecli works — agents can run a small allow-list of trusted binaries
to produce office files — but general git / npm / arbitrary shell is denied.
We have never enabled full tools.exec for the dev agents.
So how does an OpenClaw agent "code"?
Only by delegation — handing the work to a sub-process that does have a shell:
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.
- yesterday First seen · 106 lines · 0 tokens per session scan A 278a28a42c8e
AGENT_CODING_CAPABILITY is an agent published in the GitHub repository Team-Commonly/commonly (1,323 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,543 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 agents, from other repositories
deployable-inventory
Read this inventory before changing runtime configuration, release workflows, or revision evidence. A successful build proves only that an artifact was built. Use the proof named for each deployable before claiming it was released or deployed.
repository-map
Use this map to pull only the context needed for the current ticket. Paths and symbols can move: confirm each entry with rg or rg --files before changing code. Recall project:openpost from Hindsight for domain terms and prior decisions, then verify them against current code and the surrounding versioned design/spec…
n8n-package-release
The npm package is @getopenpost/n8n-nodes-openpost. Its SemVer is independent from the OpenPost app version.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Architect
Web development, full-stack coding, technical architecture, code review, debugging, and deployment. Use for any web development, coding, or technical implementation tasks.
Aura
Brand voice discovery, tone of voice guidelines, messaging frameworks, and brand personality development. Use for any branding, voice, or identity tasks.