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 skills/rayforcedb/raysense/verifynpx skills add RayforceDB/raysense --skill verifygit clone --depth 1 https://github.com/RayforceDB/raysenseWhat 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.00039 | $0.00613 |
| Opus 5 | $0.00019 | $0.00307 |
| Sonnet 5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
verify 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 2d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
Call this after a meaningful chunk of edits — typically before
suggesting the user run tests or commit. It rescans the project and
diffs the result against the baseline that bootstrap
established.
All tools take a path argument; pass the current repo root as an
absolute path.
Steps
- Rescan — call
raysense_rescanwithpath: <cwd>. Forces a fresh walk; uses cached config and plugin state. - Rule status — call
raysense_check_rules. Pass/fail per rule. A rule that was passing at bootstrap and is failing now is a regression to flag explicitly. - Baseline diff — call
raysense_baseline_diffwithpath: <cwd>. Health-dimension deltas vs the saved baseline. Anything that dropped a grade letter (B → C, etc.) is worth surfacing. - Remediations on regression — if step 2 or 3 reports
regressions, call
raysense_remediationsfor suggested fixes. Surface the regression and the suggestion to the user before continuing.
What to surface to the user
Be concise. The user does not want a wall of metrics. A good verify report is:
- "Rules: all pass" or "Rules: 1 new failure (
max_blast_radius, was 18 / threshold 25 / now 27)." - "Baseline diff: modularity B → C-, redundancy stable, others unchanged." Only the dimensions that moved.
When to skip
- Edits were limited to comments, docs, or config that does not affect imports.
- The session bootstrapped less than a minute ago and the working
tree shows trivial changes (
git diff --statis one or two lines).
See also
For verify checks the typed tools don't cover natively:
raysense_policy_check-- evaluates.rflfiles in<repo>/.raysense/policies/. Use this when the team has shipped custom architectural rules; they fire alongside the built-inraysense_check_rulesbut are code-reviewable in the repo. Exit code 1 = a policy itself failed to evaluate, 2 = at least one error-severity finding.raysense_baseline_query-- the query skill covers the syntax. Useful when a verify-time question is shaped like "did any new file land that violates X" and X needs a custom Rayfall expression.
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.
- 2d ago First seen · 63 lines · 39 tokens per session scan A 6bbf22e996c1
verify is a skill published in the GitHub repository RayforceDB/raysense (11 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 613 once invoked, about $0.0002 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.
Other skills, from other repositories
coverage-loop
Iteratively improve Fallow Rust test coverage with cargo-llvm-cov, prioritizing meaningful untested behavior and preserving runtime correctness.
ci-formats-review
Review SARIF, CodeClimate, compact, markdown, badge, and other CI-facing output formats for correctness and integrator expectations. Use when changes affect machine-consumed report formats or CI presentation layers.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
deps-audit
Audit dependencies for vulnerabilities, staleness, unused packages, and license risks — produce a health report with actionable fixes.