Borrowing it
Nothing to install: this file belongs to global-mysterysnailrevolution/physical-capability-cloud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/global-mysterysnailrevolution/physical-capability-cloud/master/CLAUDE.mdgit clone --depth 1 https://github.com/global-mysterysnailrevolution/physical-capability-cloudWrote 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/global-mysterysnailrevolution/physical-capability-cloud/claude-md)<a href="https://agentmods.dev/instructions/global-mysterysnailrevolution/physical-capability-cloud/claude-md"><img src="https://agentmods.dev/badge/instructions/global-mysterysnailrevolution/physical-capability-cloud/claude-md/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/instructions/global-mysterysnailrevolution/physical-capability-cloud/claude-md"><img src="https://agentmods.dev/badge/instructions/global-mysterysnailrevolution/physical-capability-cloud/claude-md.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.10880 | $0.10880 |
| Opus 5 | $0.05440 | $0.05440 |
| Sonnet 5 | $0.02176 | $0.02176 |
| Haiku 4.5 | $0.01088 | $0.01088 |
Grade C, and why
physical-capability-cloud CLAUDE.md scanned grade C with 4 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 11d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
Dangerous keywords (rm -rf, git reset --hard, git push --force, drop table, curl | sh) are scored 0.0-1.0. Actions scoring >0.5 are dual-logged and may be denied per agent allowlist. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Configuration** (add to Claude Code settings or `~/.claude/settings.json`): Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Dangerous keywords (rm -rf, git reset --hard, git push --force, drop table, curl | sh) are scored 0.0-1.0. Actions scoring >0.5 are dual-logged and may be denied per agent allowlist. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Dangerous keywords (rm -rf, git reset --hard, git push --force, drop table, curl | sh) are scored 0.0-1.0. Actions scoring >0.5 are dual-logged and may be denied per agent allowlist. How it starts
The opening of the file, as written. The whole thing — 990 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY: DGX Spark Offload
ALWAYS check Spark availability (spark-check) at session start and offload ALL builds, tests, and heavy work to the DGX Spark (192.168.108.72, 119GB RAM). The local machine has only 16GB RAM and WILL OOM on builds, parallel tests, and multi-agent workloads. Use spark-run for everything. No exceptions.
spark-run "cd ~/projects/physical-capability-cloud && pnpm build --concurrency=1"— buildspark-run "cd ~/projects/physical-capability-cloud && pnpm --workspace-concurrency=1 -r test"— testspark-run "cd ~/projects/physical-capability-cloud && pnpm install"— install- If Spark is down, use
--concurrency=1locally and warn the user about OOM risk.
MANDATORY: Security — Gate A Vetting Pipeline
All new tools, MCP servers, npm packages, and external dependencies MUST pass through Gate A vetting before being approved for use in this project.
How to Vet
- Run
/vet <package-path>on any new tool/package before integration - Runs up to 7 scanners: Trivy (vulns+SBOM), Gitleaks (secrets), ClamAV (malware), npm audit, pip-audit, Semgrep (SAST), prompt injection detection
- Scanners degrade gracefully if not installed. Prompt injection scanner always runs.
Policy Thresholds (from ~/.claude/plugins/vetting-policy.json)
- Critical vulnerabilities: 0 allowed (auto-reject)
- High vulnerabilities: max 2 (warn on any)
- Medium vulnerabilities: max 10
- Secrets in source: 0 allowed (auto-reject)
- Malware: auto-reject, no override
- Prompt injection signals: max 1 (warn on any)
Verdicts
- PASS: Clean, auto-approved
- WARN: Suspicious findings, human reviews before use
- FAIL: Critical vulns, secrets, or malware — auto-rejected
When to Vet
- Before adding any new npm dependency to any package
- Before integrating any MCP server
- Before running any third-party script
- After forging a new MCP server with
/forge - Reports saved to
ai/supervisor/forge_approvals/
MANDATORY: Action Classification
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.
- 11d ago First seen · 990 lines · 10,880 tokens per session scan C 0de3dd8eae30
physical-capability-cloud CLAUDE.md is an instructions file published in the GitHub repository global-mysterysnailrevolution/physical-capability-cloud (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 10,880 tokens to every session, about $0.0544 per session on Opus 5. A static security scan graded it C with 4 findings (downloads and executes remote code, reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).
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.