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 skills add RayforceDB/raysense --skill bootstrapgit clone --depth 1 https://github.com/RayforceDB/raysenseWrote 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/skills/rayforcedb/raysense/bootstrap)<a href="https://agentmods.dev/skills/rayforcedb/raysense/bootstrap"><img src="https://agentmods.dev/badge/skills/rayforcedb/raysense/bootstrap/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/skills/rayforcedb/raysense/bootstrap"><img src="https://agentmods.dev/badge/skills/rayforcedb/raysense/bootstrap.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.00052 | $0.00665 |
| Opus 5.5 | $0.00021 | $0.00266 |
| Sonnet 5.5 | $0.00010 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00067 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap
Run this once per session, before any non-trivial edits. It produces a
persisted baseline plus live splayed-table memory that the other
raysense skills (impact, verify,
audit) read against.
All tools take a path argument. Always pass the current working
directory as an absolute path so per-project state stays inside the
repo (<repo>/.raysense/).
Steps
- Health overview — call
raysense_healthwithpath: <cwd>. Note the overall grade and the worst dimension. - Save the baseline — call
raysense_baseline_savewithpath: <cwd>. This writes<cwd>/.raysense/baseline/manifest.jsonplus splayed tables under<cwd>/.raysense/baseline/tables/. - Confirm memory is live — call
raysense_memory_summarywithpath: <cwd>. Report the row/column counts so the user can see the memory is materialized. - Surface the top 3 hotspots — call
raysense_hotspotsandraysense_rules. List the three highest-traffic files and any already-failing rules. These are the spots most likely to bite during the session.
What to keep in working memory
After bootstrap, the agent should remember (briefly):
- The overall health grade and the lowest-scoring dimension.
- The three hottest files (high coupling × high churn).
- Whether any rules are currently failing (so a later regression isn't mistaken for pre-existing breakage).
When to skip
- Session is read-only (the user just asked a question -- no edits
planned). Skip bootstrap; reach for
auditinstead if structural context is needed. - A baseline already exists from a recent session and no commits have
landed since (
git log -1 --since='1 hour ago'shows nothing). Re-using the previous baseline is fine; just callraysense_healthfor a fresh grade and skip the rest.
See also
The baseline this skill produces is queryable, not just a dump. After bootstrap, the agent has access to:
raysense_baseline_query-- run any Rayfall expression against a saved table. Syntax and worked examples in the query skill (select /.graph.*/ Datalog / vector search).raysense_policy_check-- evaluate.rflpolicy packs in<repo>/.raysense/policies/; ships its own exit-code semantics for CI gating.raysense_baseline_import_csv-- bring external CSVs (coverage, lint counts, embeddings) into the baseline as queryable tables.
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 · 64 lines · 52 tokens per session scan A 0fb8e0b0ea95
bootstrap is a skill published in the GitHub repository RayforceDB/raysense (13 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 665 once invoked, about $0.0002 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-30.
Other skills, from other repositories
permanent-memory-loader
Loads permanentmemory.md summary lines (≤120 always-loaded tokens, hard cap 200). Surfaces durable wisdom from past Epics into the current session. Silent if .claude/memory/ does not exist.
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…
gohm
/gohm - Go Harvest Memory (Knowledge Harvester).
context
Context Manager - Token Budget Controller.
memory
Use this agent to manage permanent memory storage, retrieval weight calculation, and knowledge preservation following NASAB Pillar 5.
recall
/recall — Layered Knowledge Recall.