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/impactnpx skills add RayforceDB/raysense --skill impactgit 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.00046 | $0.00676 |
| Opus 5 | $0.00023 | $0.00338 |
| Sonnet 5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
impact 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.
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.
Impact
Call this before a non-trivial edit (deletion, rename, signature change, extraction, file move). It tells the agent what depends on the target and what the target depends on, so the edit plan can account for the blast radius up front.
All tools take a path argument (absolute, current repo root) plus
the target file path relative to that root.
Steps
- Blast radius — call
raysense_blast_radiuswithpath: <cwd>andfile: <target>. Returns the set of files reachable downstream under the active edge filter. A blast radius >20 files is a strong signal to break the change into smaller commits. - Coupling profile — call
raysense_coupling. Look up the target's module in the response: afferent (incoming) and efferent (outgoing) counts, plus main-sequence distance. High-afferent modules are stable foundations — breaking changes there cascade widely. - Cycle exposure — call
raysense_cycles. If the target appears in any reported cycle, callraysense_break_cycle_recommendationsfor ranked candidate edges to remove. The recommended edge is often not the obvious one. - Optional simulation — when the planned change is mechanical
(file removal, edge removal), call
raysense_what_ifto preview the health delta without touching the working tree.
What to keep in working memory
- Number of files in the blast radius — quote it back to the user before starting an edit that exceeds 20.
- Whether the target is on any cycle — informs whether the edit is likely to introduce or break a cycle.
- The
instabilityscore — a value near 1.0 means the file is expected to depend on stable foundations, not be one.
When to skip
- Local-only edit inside one file with no signature changes (typo fix, comment, internal rename). No downstream effect, no need.
- Brand-new file. Nothing depends on it yet.
See also
For cases the typed tools above don't cover, the query
skill exposes Rayfall directly via raysense_baseline_query:
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.
- yesterday First seen · 64 lines · 46 tokens per session scan A 9c119c990b1c
impact is a skill published in the GitHub repository RayforceDB/raysense (11 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 676 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.