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/lamasu/physical-capability-cloud/agents-mdgit clone --depth 1 https://github.com/LamaSu/physical-capability-cloudWhat 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
physical-capability-cloud 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 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.
This is a copy
88% identical to physical-capability-cloud AGENTS.md — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCC -- Physical Capability Cloud
What This Is
AWS for the physical world. A decentralized cloud control plane where AI agents discover, negotiate, and orchestrate physical manufacturing capabilities -- 3D printers, CNC routers, liquid handlers, mass spectrometers, couriers -- through on-chain milestone escrow with cryptographic evidence. Operators register what their machines can do; agents handle everything else.
Live at capability.network.
Architecture
| Package | Role |
|---|---|
packages/spec |
All types, schemas, Zod validation (single source of truth) |
packages/contracts |
Solidity MilestoneEscrow, soulbound NFTs, reward engine |
packages/db |
SQLite shared database layer |
packages/kernel |
Shop Kernel runtime: device adapters, evidence emitter |
packages/gateway |
Fastify HTTP gateway, 40+ route files, SSE streams |
packages/scheduler |
Workflow DAG compiler + capability router |
packages/verifier |
Evidence verification + Bittensor subnet |
packages/payments |
x402 micropayments + Meteora DLMM pricing pools |
packages/identity-8004 |
ERC-8004 identity/reputation/validation registries |
packages/a2a |
Agent-to-Agent typed intent bus (34 intents) |
packages/agent-runtime |
Base agent framework: wallet, tools, intent handlers |
packages/agent-user |
User Agent: discover, negotiate, submit workflows |
packages/agent-broker |
Broker Agent: route capabilities, compile DAGs |
packages/agent-kernel |
Kernel Agent: accept jobs, emit evidence |
packages/agent-evaluator |
Evaluator Agent: quality assessment, attestation VCs |
packages/agent-support |
Support Agent: diagnostics, escalation, setup guidance |
packages/pcc-node |
Python CLI for operators (pip install pcc-node) |
packages/dht |
WebSocket gossip DHT for decentralized discovery |
packages/mcp-server |
56 MCP tools over stdio |
packages/contract-builder |
Interactive capability contract builder |
packages/onboard-kit |
Operator scaffolding CLI |
packages/orchestrator |
Multi-instrument workflow orchestration |
apps/dashboard |
Vite + React 19 dashboard (57+ routes) |
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 · 132 lines · 1,554 tokens per session scan A 0efe746f290f
physical-capability-cloud AGENTS.md is an instructions file published in the GitHub repository LamaSu/physical-capability-cloud (1 stars, last pushed 3d ago), licensed Apache-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. It is 88% identical to physical-capability-cloud AGENTS.md, differing in 20 lines, and is treated as a copy.
Other instructions, from other repositories
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.