piclaw-addons: Instructions file for Codex

AGENTS.md

piclaw-addons AGENTS.md is an instructions file for Codex, OpenCode from rcarmo/piclaw-addons. It costs 3,149 tokens per session, scanned A, original, MIT.

A set of repository instructions for developing and publishing piclaw add-ons, which are extensions for the piclaw project.

In plain words
What is it for?
Use it to create an add-on directory, write its entry point and package files, sync the catalog, run checks and tests, package it, and prepare a pull request.
Why use it?
It explains the required add-on layout, installation rules, catalog updates, validation commands, and contribution workflow so changes meet the repository's expectations.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is rcarmo/piclaw-addons's own configuration. It tells Codex and OpenCode how to work on piclaw-addons itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything piclaw-addons configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is 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 directo.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/rcarmo/piclaw-addons/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rcarmo/piclaw-addons

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for piclaw-addons AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rcarmo/piclaw-addons/agents-md/github.svg)](https://agentmods.dev/instructions/rcarmo/piclaw-addons/agents-md)
Your own site
<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.

agentmods 80×15 button for piclaw-addons AGENTS.md

Your own site · 80×15
<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>
Per session 3,149 This file is loaded in full into every session.
When invoked 3,149 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash f743ad9dfff0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

AGENTS.md · 356 lines

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-addons must install via public GitHub-hosted tarball URLs from catalog.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" }] };
    },
  });
}

Read the full file on GitHub · 356 lines

Changes

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.

  1. 1mo ago Changed · +4 lines · +156 tokens per session f743ad9dfff0
  2. 2mo ago First seen · 352 lines · 2,993 tokens per session scan A 302261a0a474

Subscribe to this mod's changes

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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

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.

denoland/deno · 3,077 tokens