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 instructions/dfridkin/clawops/agents-mdgit clone --depth 1 https://github.com/dfridkin/clawopsWhat 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.01554 | $0.01554 |
| Opus 5 | $0.00777 | $0.00777 |
| Sonnet 5 | $0.00311 | $0.00311 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
clawops 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clawops CLAUDE.md — 86% identical, 24 lines differ
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clawops
clawops is a TypeScript CLI that generates and applies infrastructure to deploy self-hosted OpenClaw across AWS, GCP, Azure, and local VMs. It uses the Pulumi Automation API (embedded engine, not user-installed) and exposes its operations as both a CLI surface and an MCP server so Claude Code, Cursor, and other agents can drive deployments deterministically.
Directory map
src/cli/citty-based commands (one file per verb incommands/)src/providers/one folder per cloud; each implementsProviderAdapter(src/providers/types.ts, GENERATED fromspec/providers.schema.json)src/pulumi/Pulumi components + Automation API wrapper. URN convention:clawops:<cat>:<Name>where category ∈ {infra, build, net, app, state}src/mcp/MCP server, tool definitions auto-generated fromspec/mcp-tools.yamlsrc/transport/SSH (usesssh2). Never shell out to/usr/bin/sshsrc/plan/Maker plan generation, validation (ajvagainstspec/deploy-plan.schema.json), applysrc/config/~/.clawops/config.jsonmanagement (no secrets — see R6)spec/machine-readable specs (JSON Schema, YAML). Treat as ground truth (R-meta-1)docs/narrative architecture, ADRs, per-provider guides.claude/skills/invokable procedures (/add-provider,/release,/openclaw-config,/tdd).claude/rules/path-scoped rules loaded on demand
Commands
pnpm devrun CLI from srcpnpm buildtsup build to dist/pnpm testvitest, parallelpnpm test:changedvitest --changed; use this during edit loopspnpm typechecktsc --noEmitpnpm linteslint --max-warnings=0pnpm gen:schemasemitsrc/providers/types.tsandsrc/mcp/tools/_generated.tsfromspec/pnpm gen:schemas --checkCI check that committed generated files match specpnpm changesetrecord a release note (see/releaseskill)
Invariants — YOU MUST follow these
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.
- 2d ago First seen · 95 lines · 1,554 tokens per session scan A d3af0174b141
clawops AGENTS.md is an instructions file published in the GitHub repository dfridkin/clawops (1 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 1,554 tokens to every session, about $0.0078 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-31.
Other instructions, from other repositories
apex-accelerator iac-bicep-best-practices.instructions.md
Bicep-specific IaC best practices for Azure templates. Security baseline, naming, AVM mandate, anti-patterns.
awsmux AGENTS.md
Instructions for 0hardik1/awsmux, covering agents.md, what awsmux is, build, test, verify, layout and the safety model — invariants you must not weaken.
terraform-provider-pipefy AGENTS.md
Instructions for pipefy/terraform-provider-pipefy, covering agents.md, project overview, setup and requirements, essential commands and project layout.
plan-forge azd.instructions.md
Azure Developer CLI (azd) patterns — azure.yaml structure, infra folder, tags, hooks, pipelines.
plan-forge terraform.instructions.md
Terraform Azure patterns — file structure, providers, state, naming, security, testing.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.