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/pilotspace/pilot-space/claude-mdgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/claude-md)<a href="https://agentmods.dev/instructions/pilotspace/pilot-space/claude-md"><img src="https://agentmods.dev/badge/instructions/pilotspace/pilot-space/claude-md.svg" alt="Measured on agentmods" 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 | $0.02337 | $0.02337 |
| Opus 5 | $0.01169 | $0.01169 |
| Sonnet 5 | $0.00467 | $0.00467 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
pilot-space 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 3d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pilot Space - AI-Augmented SDLC Platform
Built on "Note-First" paradigm - Think first, structure later.
Project Overview
AI-augmented SDLC on a "Note-First" paradigm — users write in a note canvas, AI provides ghost text completions, extracts issues from text, and reviews PRs. Human-in-the-loop on all destructive actions (DD-003). BYOK — no AI cost pass-through. Scale: 5-100 members/workspace. Details: docs/BUSINESS_CONTEXT.md
Monorepo Structure
backend/ Python FastAPI, Clean Architecture, SQLAlchemy async, DI (README.md)
frontend/ Next.js App Router, MobX + TanStack Query, shadcn/ui (README.md)
cli/ pilot-cli — `pilot login`, `pilot implement` (pyproject.toml)
authcore/ Supabase Auth self-hosted (docker-compose.yml)
infra/ Docker, Supabase local stack
docs/ Design decisions, dev patterns, specs (synced from pilotspace/pilot-space-docs)
specs/ Feature specifications (synced from pilotspace/pilot-space-docs)
scripts/ Utility scripts
design-system/ Design tokens and references
Commands
# Install
cd backend && uv sync # Backend deps
cd frontend && pnpm install # Frontend deps
make sync-docs # Sync .planning submodule (pilotspace/pilot-space-docs)
# Dev servers
cd backend && uv run uvicorn pilot_space.main:app --reload --port 8000
cd frontend && pnpm dev # port 3000
# Quality gates (run before every commit)
make quality-gates-backend # pyright + ruff check + pytest --cov
make quality-gates-frontend # eslint + tsc --noEmit + vitest
# Backend only
cd backend && uv run ruff check # Lint
cd backend && uv run ruff check --fix # Lint autofix
cd backend && uv run pyright # Type check
cd backend && uv run pytest # All tests
cd backend && uv run pytest tests/cli/ -q # CLI tests only
# Frontend only
cd frontend && pnpm lint # ESLint
cd frontend && pnpm type-check # tsc --noEmit
cd frontend && pnpm test # Vitest
cd frontend && pnpm test:e2e # Playwright
# CLI
cd cli && uv run pilot login
cd cli && uv run pilot implement PS-1 # Interactive
cd cli && uv run pilot implement PS-1 --oneshot # Non-interactive (CI)
# Migrations
cd backend && alembic heads # Verify single head
cd backend && alembic check # Head matches models
cd backend && alembic upgrade head
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.
- 3d ago First seen · 183 lines · 2,337 tokens per session scan A c87cd7108f74
pilot-space CLAUDE.md is an instructions file published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,337 tokens to every session, about $0.0117 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
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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.