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/plugins/rayforcedb/raysense/claude-plugin)<a href="https://agentmods.dev/plugins/rayforcedb/raysense/claude-plugin"><img src="https://agentmods.dev/badge/plugins/rayforcedb/raysense/claude-plugin/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/plugins/rayforcedb/raysense/claude-plugin"><img src="https://agentmods.dev/badge/plugins/rayforcedb/raysense/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
raysense 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
{
"name": "raysense",
"version": "0.5.0",
"description": "Architectural telemetry for AI coding agents. Phase-scoped skills + slash commands over the raysense MCP server: scan + baseline at session start, blast-radius before edits, regression diff after, on-demand architecture audits, time-window drift detection.",
"author": {
"name": "Anton Kundenko",
"email": "[email protected]"
},
"homepage": "https://github.com/RayforceDB/raysense",
"repository": "https://github.com/RayforceDB/raysense",
"license": "MIT",
"keywords": [
"architecture",
"code-quality",
"mcp",
"agent-loop",
"structural-health",
"coupling",
"cycles",
"blast-radius",
"memory",
"raysense"
]
}
What it installs
The manifest is a name and a version. 6 skills, 6 commands, 1 MCP server travel with it, and installing the plugin installs all of them — 591 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill query A 181 tokens
- Skill drift A 75 tokens
- Skill audit A 55 tokens
- Skill bootstrap A 52 tokens
- Skill impact A 46 tokens
- Skill verify A 39 tokens
- Command query A 22 tokens
- Command audit A 25 tokens
- Command bootstrap A 25 tokens
- Command impact A 23 tokens
- Command drift A 23 tokens
- Command verify A 25 tokens
- MCP server raysense A not measured
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 · 25 lines scan A d033918a4a85
raysense is a plugin published in the GitHub repository RayforceDB/raysense (13 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
fuse-changelog
Claude Code update watcher: changelog tracking, breaking changes detection, community pulse via Exa, plugin compatibility analysis.
antidote
Stop AI agents from patching symptoms. Forces structural root-cause fixes over symptom patching in any language or stack.
codeeraser
CodeEraser passive guard + erase skill: a winnowing clone index behind a per-project daemon intercepts T1/T2 duplicate writes at PreToolUse (with the tombstone and flow legs judged in the core), records at PostToolUse whether an asked write ran (settle), audits net LOC + touched duplicates at Stop, and reports health…
vg
Vibgrate AI Context for Claude Code: a local-first MCP server with a deterministic code map (impact, navigation, search) plus version-correct, drift-annotated library docs. No API key.
n1-optimizer
Parallel performance analysis tool that identifies N+1 queries, inefficient APIs, and suboptimal code patterns across your entire application stack.