thepopebot: Instructions file for Claude Code

CLAUDE.md

thepopebot CLAUDE.md is an instructions file for Claude Code from stephengpope/thepopebot. It costs 2,915 tokens per session, scanned A, original, MIT.

Repository instructions for working on thepopebot, an npm package that runs coding jobs in Docker containers and can create pull requests automatically.

In plain words
What is it for?
Use them when modifying the npm package, its Next.js event handler, Docker setup, paths, deployment, or agent-job workflow.
Why use it?
They explain where package code, user files, logs, and mounted directories belong, reducing mistakes when changing or deploying the system.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is stephengpope/thepopebot's own configuration. It tells Claude Code how to work on thepopebot 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 thepopebot configures →

About the project

The Pope Bot is an app for configuring an autonomous AI agent that can chat, run coding work, and operate continuously through connected language models and coding agents. People use it for questions, code changes, background development jobs, and live browser-based coding sessions. Its catalogue add-ons extend the bot with commands, skills, and operating instructions.

stephengpope/thepopebot · 1,860 stars · on GitHub · skool.com

Reuse

Borrowing it

Nothing to install: this file belongs to stephengpope/thepopebot. 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/stephengpope/thepopebot/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/stephengpope/thepopebot

Made for: Claude Code.

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 thepopebot CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/stephengpope/thepopebot/claude-md.svg)](https://agentmods.dev/instructions/stephengpope/thepopebot/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/stephengpope/thepopebot/claude-md"><img src="https://agentmods.dev/badge/instructions/stephengpope/thepopebot/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,915 This file is loaded in full into every session.
When invoked 2,915 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.02915 $0.02915
Opus 5 $0.01458 $0.01458
Sonnet 5 $0.00583 $0.00583
Haiku 4.5 $0.00292 $0.00292

Measured 8d ago against content hash 6bb01548e947, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

thepopebot CLAUDE.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 8d 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.

CLAUDE.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

thepopebot — Package Source Reference

Technical reference for AI assistants modifying the thepopebot NPM package source code.

Architecture: Event Handler (Next.js) creates agent-job/* branches → launches Docker agent container locally (Claude Code, Pi, etc.) → task executed → PR created → auto-merge → notification. Agent jobs log to logs/{JOB_ID}/.

Deployment Model

The npm package (api/, lib/, config/, bin/) is published to npm. In production:

  • Event handler: Docker image bakes the npm package, Next.js app source (web/), and .next build output. User project directories (agent-job/, event-handler/, skills/, skills-library/, .env, data/, etc.) are individually volume-mounted into /app. The full project is also mounted at /project for git access. Runs server.js via PM2 behind Traefik reverse proxy.
  • lib/paths.js: Exports PROJECT_ROOT (process.cwd()). This is how the installed npm package finds the volume-mounted user project files.
  • Agent-job containers: Ephemeral Docker containers clone agent-job/* branches separately — use named volumes for workspace. See docker/CLAUDE.md.
  • Local install: Gives users CLI tools (init, setup, upgrade) and configuration scaffolding.

Package vs. Templates — Where Code Goes

All event handler logic, API routes, library code, and core functionality lives in the npm package (api/, lib/, config/, bin/). This is what users import when they import ... from 'thepopebot/...'.

The templates/ directory contains only files that get scaffolded into user projects via npx thepopebot init. Templates are for user-editable configuration and thin wiring — things users are expected to customize or override. Never add core logic to templates.

When adding or modifying event handler code, always put it in the package itself (e.g., api/, lib/), not in templates/. Templates should only contain:

  • Configuration files users edit (agent-job/SYSTEM.md, agent-job/CRONS.json, event-handler/TRIGGERS.json, etc.)
  • GitHub Actions workflows
  • Docker compose (docker-compose.yml)
  • CLAUDE.md files for AI assistant context in user projects

Read the full file on GitHub · 158 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. 8d ago First seen · 158 lines · 2,915 tokens per session scan A 6bb01548e947

Subscribe to this mod's changes

thepopebot CLAUDE.md is an instructions file published in the GitHub repository stephengpope/thepopebot (1,860 stars, last pushed 3mo ago), licensed MIT. It adds 2,915 tokens to every session, about $0.0146 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-30.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

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.

github/spec-kit · 7,104 tokens