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/1clawai/scaffold-agent/agents-mdgit clone --depth 1 https://github.com/1clawAI/scaffold-agentWrote 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/instructions/1clawai/scaffold-agent/agents-md)<a href="https://agentmods.dev/instructions/1clawai/scaffold-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/1clawai/scaffold-agent/agents-md.svg" alt="Measured on agentmods" 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 | $0.02279 | $0.02279 |
| Opus 5 | $0.01140 | $0.01140 |
| Sonnet 5 | $0.00456 | $0.00456 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade A, and why
scaffold-agent 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 today.
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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions — scaffold-agent
This repository is the npm CLI that generates onchain-agent monorepos (Foundry/Hardhat + Next.js/Vite/Python). It is not a generated app; consumer projects live in folders created by the CLI.
Terminology
- 1claw / 1Claw — 1claw.co: vault, agents, Shroud LLM proxy (Shroud docs), Intents API (1claw.co/intents) for HSM/TEE transaction signing across 29+ EVM chains plus Bitcoin, Solana, XRP, Cardano, and Tron.
- OpenClaw — separate product (openclaw.ai); do not confuse with 1claw.
- @1claw/mcp — MCP server with 44 tools for vault secrets, Intents API, signing keys, treasury, and execution intents.
Build and verify
npm install
npm run build # tsup → dist/cli.js
node dist/cli.js --version
After changing src/cli.ts, src/cli-argv.ts, src/cli-wizard.ts, src/agent-project-config.ts, or src/actions/scaffold.ts (templates), always run npm run build before treating the CLI as up to date.
Run the CLI locally
node dist/cli.js --help
node dist/cli.js my-project # interactive; creates ./my-project under cwd
Non-interactive / automation (-y)
Use -y / --non-interactive so no stdin prompts run (CI, scripts, other agents).
- Required when default
--secretsisoneclaw:--env-password(≥ 6 chars), unless you set--secrets none. --defer-oneclaw-api-key: omitONECLAW_API_KEYat scaffold time (vault not created until key exists).--oneclaw-intents: with-y, register the 1Claw API agent with Intents enabled (1claw.co/intents); interactive runs ask when vault setup creates an agent.--skip-npm-install/--skip-auto-fund: avoid install and fund script in automation.
Minimal example (creates ./my-app in current directory):
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.
- today Changed 5315c6d52e9c
- 4d ago First seen · 130 lines · 2,279 tokens per session scan A 40cd97fc6e50
scaffold-agent AGENTS.md is an instructions file published in the GitHub repository 1clawAI/scaffold-agent (2 stars, last pushed yesterday), licensed MIT. It adds 2,279 tokens to every session, about $0.0114 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
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).
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.
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.
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.
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).
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.