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.
/plugin marketplace add RayforceDB/raysensenpx agentmods add plugins/rayforcedb/raysense/claude-plugingit clone --depth 1 https://github.com/RayforceDB/raysenseGrade 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 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.
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 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 · 25 lines scan A d033918a4a85
raysense is a plugin published in the GitHub repository RayforceDB/raysense (11 stars, last pushed 4mo 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
codeeraser
Plugin marketplace listing 1 plugin: codeeraser.
logic-lens-marketplace
Plugin marketplace listing 1 plugin: logic-lens.
mellos-mapping
梅勒斯地图 — a live layered dependency map for bottom-up development: ghost the design first, then light nodes up from the bottom as they are built and verified.
craftsman-marketplace
Practical, opinionated craft skills for Claude Code and Codex: engineering-readiness audits for AI-built apps, and CPA-grade US tax and accounting workpapers.
devlens
Codebase intelligence for AI agents. The /devlens skill teaches your agent to query a precomputed code graph (nodes, typed edges, technical/business/security summaries) via the bundled DevLens MCP server instead of grepping and reading whole files — for TypeScript, JavaScript, Python, Go, Rust, and Java repos, with…
bullpen
The senior dev, unbundled. A cast of opinionated skills that make an AI agent push back on bad ideas, verify before it claims done, attack its own code, and finish like a senior engineer.