bootstrap

A project-start command that scans a codebase, records its current baseline, and reports its main problem areas and failing rules.

In plain words
What is it for?
Use it at the beginning of a session to check the project grade, weakest area, hottest files, stored baseline data, and pre-existing rule failures.
Why use it?
It separates existing issues from later changes and gives the session an initial view of project health.

Command

Install

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.

agentmods
npx agentmods add commands/rayforcedb/raysense/bootstrap
Clone the repo
git clone --depth 1 https://github.com/RayforceDB/raysense
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 228 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00025 $0.00228
Opus 5 $0.00013 $0.00114
Sonnet 5 $0.00005 $0.00046
Haiku 4.5 $0.00003 $0.00023

Measured yesterday against content hash 35fe96a62fd5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bootstrap 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 yesterday.

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-plugin/commands/bootstrap.md · 16 lines

What it actually says

Bootstrap a raysense session for the project at $1.

If $1 is empty, treat the project root as the current working directory.

  1. Call raysense_health with path: $1. Note the overall grade and the weakest dimension.
  2. Call raysense_baseline_save with path: $1 to persist the baseline ($1/.raysense/baseline/).
  3. Call raysense_memory_summary with path: $1 to confirm the splayed tables are live; report row/column counts.
  4. Call raysense_hotspots and raysense_rules with path: $1. List the three hottest files and any rules currently failing.

Finish with a short summary: overall grade, weakest dimension, the three hottest files, and pre-existing rule failures (so later regressions can be told apart from baseline noise).

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. yesterday First seen · 16 lines · 25 tokens per session scan A 35fe96a62fd5

Subscribe to this mod's changes

bootstrap is a command published in the GitHub repository RayforceDB/raysense (11 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 228 once invoked, about $0.0001 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.