vanguard: Instructions file for Claude Code

CLAUDE.md

vanguard CLAUDE.md is an instructions file for Claude Code from SebaBoler/vanguard. It costs 559 tokens per session, scanned B, original, MIT.

A project instruction file for Vanguard, a standalone TypeScript software framework. It records coding rules, testing requirements, and restrictions for work on that project.

In plain words
What is it for?
Use it when modifying Vanguard code to follow its TypeScript and import conventions, avoid workflow-file changes, and run its type-check and tests.
Why use it?
It gives coding agents consistent project-specific guidance and helps prevent prohibited changes or unfinished checks.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

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

Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sebaboler/vanguard/claude-md/github.svg)](https://agentmods.dev/instructions/sebaboler/vanguard/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/sebaboler/vanguard/claude-md"><img src="https://agentmods.dev/badge/instructions/sebaboler/vanguard/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.

agentmods 80×15 button for vanguard CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sebaboler/vanguard/claude-md"><img src="https://agentmods.dev/badge/instructions/sebaboler/vanguard/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 559 This file is loaded in full into every session.
When invoked 559 The same file — it is already loaded in full.
Security scan B 1 finding. 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.00559 $0.00559
Opus 5.5 $0.00224 $0.00224
Sonnet 5.5 $0.00112 $0.00112
Haiku 4.5 $0.00056 $0.00056

Measured 22d ago against content hash 3b6c36ad8c7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

vanguard CLAUDE.md scanned grade B with 1 finding 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 22d 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

- **Never modify CI config: `.github/workflows/`, `.github/actions/`, `.gitlab-ci.yml`, `.gitlab/**.yml`** (authoritative check: `workflowPaths()` in `src/core/vanguard.ts`, which also covers `.gitlab/**/*.yaml` at any d
CLAUDE.md · 22 lines

How it starts

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

CLAUDE.md

Vanguard is a standalone TypeScript framework — an autonomous software factory. Strict TypeScript, ES modules with explicit .js import extensions, Node 24+. Tests are co-located as *.test.ts (Vitest).

Hard constraints

  • Never modify CI config: .github/workflows/, .github/actions/, .gitlab-ci.yml, .gitlab/**.yml (authoritative check: workflowPaths() in src/core/vanguard.ts, which also covers .gitlab/**/*.yaml at any depth and files standing in for those directories). This is a security boundary: an agent that can commit CI config can run arbitrary code with the repo's secrets on the next event. It is also enforced mechanically — copy-back drops those paths, and the CI GITHUB_TOKEN cannot push workflow changes, so such a push is rejected and the run's work is lost. If a task seems to need a CI-config change, make the code/doc change instead and describe the needed edit in the PR body for a human to apply by hand.
  • Run pnpm typecheck and pnpm test before signalling completion.

Style

  • Match the surrounding code: comment density, naming, idiom. Keep diffs minimal.
  • Explicit return types; prefer const; early returns; functional where it fits.

Review guidance

For the PR reviewer. The CI-config constraint above binds the autonomous run (implement, revise); humans change CI config through PRs, which are reviewed, not refused.

  • A CI-config edit is not a finding for the constraint itself when the API-sourced PR author (never a name claimed in the PR text, commits or diff) passes the author gate in .github/workflows/vanguard-pr-review.yml (bots do not; Dependabot's action-pin bumps never reach this reviewer). Review the content as the highest-risk part of the diff: trigger type (pull_request_target), permissions:, actor gates, secret exposure, no ${{ }} interpolation inside run:. A CI-config edit by any other author is itself a finding.
  • The workflow-scoped token a maintainer pushes with is personal and local, never a CI secret (VANGUARD_PUSH_TOKEN must not carry workflow scope).
  • When every actionable item is on a CI-config path, say so in the verdict and do not recommend needs revision: the reviser drops edits to those paths and ends in "no changes — skipping push" without posting, leaving needs revision and vanguard:revising on the PR. With mixed feedback it fixes the rest and discloses the dropped paths.

Read the full file on GitHub · 22 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. 22d ago Changed · +8 lines · +359 tokens per session scan A → B 3b6c36ad8c7e
  2. 2mo ago First seen · 14 lines · 200 tokens per session scan A 8b7535dd0ed5

Subscribe to this mod's changes

vanguard CLAUDE.md is an instructions file published in the GitHub repository SebaBoler/vanguard (4 stars, last pushed 9d ago), licensed MIT. It adds 559 tokens to every session, about $0.0022 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens