Borrowing it
Nothing to install: this file belongs to rcarmo/piclaw-addons. 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/rcarmo/piclaw-addons/main/AGENTS.mdgit clone --depth 1 https://github.com/rcarmo/piclaw-addonsWrote 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/rcarmo/piclaw-addons/agents-md)<a href="https://agentmods.dev/instructions/rcarmo/piclaw-addons/agents-md"><img src="https://agentmods.dev/badge/instructions/rcarmo/piclaw-addons/agents-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/rcarmo/piclaw-addons/agents-md"><img src="https://agentmods.dev/badge/instructions/rcarmo/piclaw-addons/agents-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.03149 | $0.03149 |
| Opus 5.5 | $0.01260 | $0.01260 |
| Sonnet 5.5 | $0.00630 | $0.00630 |
| Haiku 4.5 | $0.00315 | $0.00315 |
Grade A, and why
piclaw-addons 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 1mo 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing piclaw add-ons
This guide covers how to create, test, and publish an extension for piclaw.
Quick start
Install-path rule: first-party
piclaw-addonsmust install via public GitHub-hosted tarball URLs fromcatalog.json. Do not change docs, generated catalog entries, or runtime integration back to npmjs.org package specs or authenticated GitHub Packages reads. Runtime install/remove must remain zero-auth.
# 1. Create your addon directory
mkdir -p addons/my-addon/skills/my-skill
# 2. Write your entry point, package.json, and skill
# 3. Sync the catalog
bun run sync:catalog
# 4. Validate the repository contracts
bun install --frozen-lockfile
bun run check:catalog
bun run typecheck:earendil-compat
bun run test:earendil-compat
bun test standalone-import.test.ts
bun pm pack --dry-run
# 5. Commit on a feature branch and open a pull request
git switch -c feat/my-addon
git add addons/my-addon package.json catalog.json
git commit -m "feat: add my-addon"
git push -u origin feat/my-addon
gh pr create
Addon structure
Important: standalone add-on packages must be self-contained. If an add-on is published as its own npm package (for example
@rcarmo/piclaw-addon-portainer), it must not rely on repo-root files outside its package directory at runtime. Do not import../../lib/compat/*from a published standalone package unless those files are vendored into that package.
addons/<slug>/
├── index.ts # Runtime entry point (default export)
├── web/
│ └── index.ts # Optional browser-side settings pane / web entry
├── package.json # Package manifest
├── skills/ # Optional: agent skills
│ └── my-skill/
│ └── SKILL.md
└── *.ts # Supporting modules
Entry point
The default export is a function that receives the ExtensionAPI:
import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
import { dirname, join } from "node:path";
import { fileURLToPath } from "node:url";
const baseDir = dirname(fileURLToPath(import.meta.url));
export default function myAddon(pi: ExtensionAPI) {
// Register skills for agent discovery
pi.on("resources_discover", () => ({
skillPaths: [join(baseDir, "skills", "my-skill", "SKILL.md")],
}));
// Register a tool
pi.registerTool({
name: "my_tool",
label: "my_tool",
description: "What this tool does.",
parameters: MyToolSchema,
async execute(_toolCallId, params, _signal, _update, ctx) {
return { content: [{ type: "text", text: "result" }] };
},
});
}
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.
- 1mo ago Changed · +4 lines · +156 tokens per session f743ad9dfff0
- 2mo ago First seen · 352 lines · 2,993 tokens per session scan A 302261a0a474
piclaw-addons AGENTS.md is an instructions file published in the GitHub repository rcarmo/piclaw-addons (23 stars, last pushed yesterday), licensed MIT. It adds 3,149 tokens to every session, about $0.0126 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.