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/appautomaton/pi-arcweld/agents-mdgit clone --depth 1 https://github.com/appautomaton/pi-arcweldWhat 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.01119 | $0.01119 |
| Opus 5 | $0.00560 | $0.00560 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
pi-arcweld 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Pi Workspace Rules
This repository wraps the upstream pi-mono source as a pinned Git submodule.
Workspace Layout
pi-mono/is an upstream Git submodule, pinned by the root repository. Keep it free of local build/dependency state and do not add it to a root npm workspace.extensions/is the single repository root for locally maintained Pi extensions. Keep every curated extension there. Global extensions may be symlinked into~/.pi/agent/extensions/or registered as local-path packages in~/.pi/agent/settings.json; document the chosen loading method inextensions/README.md.mcp-servers/holds the canonical source for locally maintained MCP servers. They are standalone processes, not Pi extensions, and each owns its package and release workflow. Develop and test them here, then deploy tested versioned releases under~/.local/mcps/<server>/releases/; Pi must run the~/.local/mcps/<server>/current/launcher registered by absolute path in~/.pi/agent/mcp.json, not the mutable Git checkout. Seemcp-servers/README.md.- Chrome DevTools MCP is external to this repository. Its single canonical root is
~/.local/mcps/chrome-devtools/; read itsAGENTS.mdandREADME.mdbefore changing the integration. The Chrome browser remains under~/.local/browsers/chrome/. system-instruction/contains the canonicalAPPEND_SYSTEM.md, symlinked from~/.pi/agent/APPEND_SYSTEM.md. Machine-specific reference captures underbaseline/are local and ignored. Do not create a project-level.pi/APPEND_SYSTEM.md, because it would replace the global append file for this project rather than layer with it.scripts/contains local runtime build, validation, and upstream-update scripts.docs/contains the static GitHub Pages site; keep its claims and paths consistent with the repository documentation.references/contains local independent repositories retained for comparison or tooling. It is ignored and is not part of the public repository.build/pi-agent/runtime/is the runnable local Pi artifact.build/pi-agent/work/is temporary build state and is deleted by default after a successful build.build/pi-agent/artifacts/contains local package tarballs used to assemble the runtime.archive/is for local logs, session exports, and other files that should not clutter the workspace root.
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 · 47 lines · 1,119 tokens per session scan A c25e6296503e
pi-arcweld AGENTS.md is an instructions file published in the GitHub repository appautomaton/pi-arcweld (6 stars, last pushed 3d ago), licensed MIT. It adds 1,119 tokens to every session, about $0.0056 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
Octop AGENTS.md
Instructions for TencentCloud/Octop, covering agents.md, 1. collaboration principles, think before writing, simplicity first and surgical edits.
nori-skillsets AGENTS.md
Instructions for tilework-tech/nori-skillsets, covering plugin package changes, claude code configuration vs. nori plugin package, skills documentation, style guide and functions and named parameters.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
llm-wiki-newsroom AGENTS.md
Instructions for alfadur7/llm-wiki-newsroom, covering llm wiki newsroom — schema & workflow instructions, how to use, directory layout, page format and ingest workflow.
llm-wiki-newsroom GEMINI.md
Instructions for alfadur7/llm-wiki-newsroom, covering llm wiki newsroom — schema & workflow instructions, how to use, directory layout, page format and ingest workflow.
open-plan-annotator AGENTS.md
Instructions for ndom91/open-plan-annotator, covering open-plan-annotator: development guide, what this is, architecture, runtime distribution and key files.