PinMe is a zero-configuration command-line tool for creating and deploying full-stack web projects with a frontend, Worker backend, and database, as well as uploading static sites. Developers and coding agents use it to launch or update frontend applications and their supporting services from one command. Its catalogue skills and instructions describe agent workflows for deploying with PinMe.
Borrowing it
Nothing to install: this file belongs to glitternetwork/pinme. 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/glitternetwork/pinme/main/CLAUDE.mdgit clone --depth 1 https://github.com/glitternetwork/pinmeWrote 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/glitternetwork/pinme/claude-md)<a href="https://agentmods.dev/instructions/glitternetwork/pinme/claude-md"><img src="https://agentmods.dev/badge/instructions/glitternetwork/pinme/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/glitternetwork/pinme/claude-md"><img src="https://agentmods.dev/badge/instructions/glitternetwork/pinme/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.00724 | $0.00724 |
| Opus 5.5 | $0.00290 | $0.00290 |
| Sonnet 5.5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
pinme 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 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.
This is a copy
92% identical to pinme AGENTS.md — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
PinMe is a zero-config CLI tool for deploying static sites to IPFS. Built with TypeScript, bundled with esbuild, published to npm as pinme. Users run commands like pinme upload dist to deploy frontends.
Build & Dev
npm run build # Production build (esbuild → dist/index.js)
npm run dev # Dev build
npm run test # Unit/integration tests (Vitest)
npm run test:cli # Real CLI black-box tests against dist/index.js
npm run verify # Full PR gate: lint, typecheck, tests, build, CLI, pack
npm run test:mutation # Slow mutation tests (manual/nightly)
Build uses build.js (esbuild), NOT rollup.config.js (legacy, unused). esbuild reads .env via dotenv at build time and injects env vars as process.env.* defines.
The output is a single CJS file at dist/index.js with a shebang, used as the pinme CLI binary.
Architecture
bin/index.ts— CLI entry point, usescommanderto register all commandsbin/*.ts— Individual command implementations (upload, save, create, bind, importCar, exportCar, delete, etc.)bin/utils/— Shared utilities:config.ts—APP_CONFIGsingleton, all API base URLs and tuning knobs from env varsapiClient.ts— Axios client factory (createPinmeApiClient,createCarApiClient)pinmeApi.ts— High-level API wrappers (domain binding, wallet, CAR export, etc.)uploadToIpfs.ts/uploadToIpfsSplit.ts— IPFS upload logic (single file vs chunked)webLogin.ts— Auth token management (reads from~/.pinme/)domainValidator.ts— Domain name validation and DNS vs subdomain detectioncliError.ts— Structured CLI error types
bin/services/uploadService.ts— Upload orchestration (hash encryption, URL generation)skills/— Claude Code skill definitions for this project
Key Patterns
- Auth: AppKey stored locally at
~/.pinme/. Auth headers injected viagetAuthHeaders()inwebLogin.ts. - API clients: Always use
createPinmeApiClient()orcreateCarApiClient()fromapiClient.ts, never raw axios. - Token expiry:
pinmeApi.tshas centralized token-expired detection (isTokenExpired) — all API calls should go through wrappers there. - Config: All env-driven config lives in
APP_CONFIG(config.ts). Don't readprocess.envdirectly elsewhere. - The
savecommand readspinme.tomlfrom project root for full-stack deploy (frontend + Cloudflare Worker + D1).
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 First seen · 52 lines · 724 tokens per session scan A 86fd8d55f964
pinme CLAUDE.md is an instructions file published in the GitHub repository glitternetwork/pinme (3,754 stars, last pushed 1mo ago), licensed MIT. It adds 724 tokens to every session, about $0.0029 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to pinme AGENTS.md, differing in 6 lines, and is treated as a copy.
Other instructions, from other repositories
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
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).