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/silouone/clensWrote 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/silouone/clens/agentic)<a href="https://agentmods.dev/plugins/silouone/clens/agentic"><img src="https://agentmods.dev/badge/plugins/silouone/clens/agentic/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/silouone/clens/agentic"><img src="https://agentmods.dev/badge/plugins/silouone/clens/agentic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
clens 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clens — 100% identical, 2 lines differ
What it actually says
{
"name": "clens",
"version": "0.4.0",
"description": "Session analysis tools for cLens — analyze distilled agent sessions, compare performance, and deep-dive into backtracking patterns",
"author": {
"name": "Silouane Galinou"
},
"homepage": "https://clens.dev"
}
What it installs
The manifest is a name and a version. 5 skills, 3 commands, 1 agent, 18 hooks travel with it, and installing the plugin installs all of them — 133 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill backtrack-analysis A 12 tokens
- Skill journey-report A 10 tokens
- Skill session-analysis A 28 tokens
- Skill session-compare A 13 tokens
- Skill session-report A 12 tokens
- Command session-report A 12 tokens
- Command session-compare A 13 tokens
- Command backtrack-analysis A 12 tokens
- Agent session-analyst A 21 tokens
- Hook ConfigChange A not measured
- Hook InstructionsLoaded A not measured
- Hook Notification A not measured
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
- Hook SessionEnd A not measured
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook SubagentStart A not measured
- Hook UserPromptSubmit A not measured
- Hook WorktreeRemove A not measured
- Hook TeammateIdle A not measured
- Hook PermissionRequest A not measured
- Hook SubagentStop A not measured
- Hook TaskCompleted A not measured
- Hook PostToolUseFailure A not measured
- Hook PreCompact A not measured
- Hook WorktreeCreate 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 · 10 lines scan A 4d4277fe7e98
clens is a plugin published in the GitHub repository silouone/clens (6 stars, last pushed 2mo 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-31.
Other plugins, from other repositories
clens
Session analysis tools for cLens — analyze distilled agent sessions, compare performance, and deep-dive into backtracking patterns.
ccmux
Drive the ccmux cross-harness CLI to dispatch work to other AI coding agents (Claude Code, Codex, Cursor, OpenCode, Pi, Gemini) through programmatic ccmux invoke calls. Requires the ccmux CLI on PATH.
sandy-cli
Sandy: sandboxed TypeScript execution for AWS queries via the sandy CLI.
supsub-cli
Agent skills for the SupSub CLI: auth / sub / search / mp / focus / group / unread / deepread.
vibegroup
Ask peer Claude Code agents in other repos and machines what they're working on, over an end-to-end-encrypted relay. Answers come from their live session via Claude Code Channels.
graph-engineering
Runs coding work as an explicit execution graph (DAG) instead of a natural-language conversation. Deterministic work is executed by the server with zero LLM calls, the points where a human steps in are declared in the graph, and run state is owned by the server rather than the conversation.