What is aboard CLAUDE.md?

A project instruction file for the aboard codebase, an application that organizes forecasts, problem analyses, and structured debates around shared claims. It documents how to run the project, where its code lives, and which checks are required.

Use it when developing aboard to install dependencies, run the app, build it, check types, lint, run tests, validate forecast criteria, and check generated URLs and configuration.

It gives a coding agent the repository's working rules and validation commands before it changes code. This helps avoid missing project-specific checks such as type checking, tests, linting, or build verification.

How ostin-pil/aboard configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ostin-pil/aboard. 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/ostin-pil/aboard/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/ostin-pil/aboard

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ostin-pil/aboard/claude-md/github.svg)](https://agentmods.dev/instructions/ostin-pil/aboard/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/ostin-pil/aboard/claude-md"><img src="https://agentmods.dev/badge/instructions/ostin-pil/aboard/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ostin-pil/aboard/claude-md"><img src="https://agentmods.dev/badge/instructions/ostin-pil/aboard/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 5,827 This file is loaded in full into every session.

When invoked 5,827 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.

Model	Per session	Once invoked
Fable 5.1	$0.05827	$0.05827
Opus 5.5	$0.02331	$0.02331
Sonnet 5.5	$0.01165	$0.01165
Haiku 4.5	$0.00583	$0.00583

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

Security

Grade A, and why

aboard 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 2mo 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 · 230 lines

How it starts

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

@AGENTS.md

aboard

An agent-first board of falsifiable claims about systemic problems facing humanity. Three modules over a shared claim graph: predictions (time-boxed forecasts), problem trees (symptom → mechanism → leverage point), and adversarial debates (steel-manned dual-dossier with ranked cruxes). Every claim is published as machine-readable JSON-LD by default.

Run

npm install
npm run dev          # http://localhost:3000
npm run build        # production build (full type-check)
npx tsc --noEmit     # type-check only, faster
npm run lint         # eslint; session-end and CI both gate on it (only reader of .js/.mjs)
npm run test         # vitest
npm run lint:resolution   # forecast resolution-criteria rigor; session-end and CI gate on --strict
npm run typecheck:mcp     # mcp-server/, which the root tsconfig excludes
npm run typecheck:clients # clients/, likewise excluded
npm run check:built-urls  # asserts over out/; run it after a build
npm run check:config      # ci.yml + wrangler.jsonc; the only reader either has
npm run check:exports     # knip; dead exports, which nothing else in the gate sees
shellcheck $(git ls-files '*.sh')   # shell scripts; session-end and CI both gate on it

lint:resolution reports forecasts a distrustful reader could not settle: criteria resolving on an utterance, criteria with no checkable threshold, and forecasts with no resolutionSource. Forecasts marked supersededBy are skipped and listed — their criteria are historical record, repaired by the replacements they name. Warn-only by default and outside npm run build, but the session-end gate runs it with --strict (build_commands in .claude/lifecycle-manifest.md), so a session cannot land a forecast a distrustful reader could not settle.

The repo's two shell scripts are bin/check-prose.sh, which is the prose gate itself, and scripts/publish-registry.sh, which handles a signing key and writes to a public registry. Both are executable behaviour that no Node command here can reach, so shellcheck runs in build_commands and as the first step in CI. That is also why "*.sh" is in code_globs: the classification only means something because a shell-aware command sits behind it.

Read the full file on GitHub · 230 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.

2mo ago First seen · 230 lines · 5,827 tokens per session scan A ba59747d7204

Subscribe to this mod's changes

aboard CLAUDE.md is an instructions file published in the GitHub repository ostin-pil/aboard (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 5,827 tokens to every session, about $0.0233 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-31.

Research ai-agents humanitarian mcp

aboard CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aboard CLAUDE.mdostin-pil/aboard	Instructions file	2	29d ago	Apache-2.0	A	5,827	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

aboard: Instructions file for Claude Code