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.
git 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/commands/rayforcedb/raysense/query)<a href="https://agentmods.dev/commands/rayforcedb/raysense/query"><img src="https://agentmods.dev/badge/commands/rayforcedb/raysense/query/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/commands/rayforcedb/raysense/query"><img src="https://agentmods.dev/badge/commands/rayforcedb/raysense/query.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.00022 | $0.00298 |
| Opus 5.5 | $0.00009 | $0.00119 |
| Sonnet 5.5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
query 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.
What it actually says
Answer the following structural question against the raysense baseline at $1:
$2
The first argument is the project path; everything after it is the question. If the project path is missing, treat it as the current working directory and the entire $ARGUMENTS as the question.
- Call
raysense_baseline_tableswithpath: $1to see the available tables and their columns. - Decide the query shape:
- Select (filter / project / aggregate) — for "files where X and Y" style questions.
- Graph algorithm (
.graph.pagerank,.graph.louvain,.graph.topsort,.graph.shortest_path,.graph.k_shortest,.graph.betweenness,.graph.closeness,.graph.bfs,.graph.mst) — for centrality, clustering, or reachability. - Datalog (transitive closure:
reaches,depends-on,tainted-by) — for declarative reachability.
- Call
raysense_baseline_querywithpath: $1and the chosen Rayfall expression.
Show the query you ran, then the result, then a one-line interpretation.
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 · 20 lines · 22 tokens per session scan A ecfafa49adf6
query is a command published in the GitHub repository RayforceDB/raysense (13 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 298 once invoked, about $0.0001 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 commands, from other repositories
deep-code-analysis
Comprehensive codebase investigation using research-expert for documentation, explore-codebase for structure, and deep analysis. Perfect for understanding complex systems.
watch
Check for Claude Code updates, detect breaking changes, analyze plugin compatibility, and optionally gather community pulse via Exa.
test-and-fix
Run tests, auto-fix fmt and lint, and fix failures until green or stuck.
improve
/improve Scan and fix all improvement categories /improve arch Architectural improvements only /improve duplication Duplicate code / abstraction consolidation /improve quality Code quality (GuardLoop patterns GL-01 through GL-10) /improve security Security posture improvements /improve --dry-run Show what would be…
ops
You are the Ops Tooling Generator, an operational tooling specialist. You generate production-ready admin panels, debug overlays, and feedback systems for completed projects.
fix
Quick bugfix commit. Use for fix bug, bugfix, patch, hotfix, correct error.