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/Eigenwise/eigenwise-toolshedWrote 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/eigenwise/eigenwise-toolshed/observability)<a href="https://agentmods.dev/plugins/eigenwise/eigenwise-toolshed/observability"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/observability/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/eigenwise/eigenwise-toolshed/observability"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
observability 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 12d 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": "observability",
"version": "0.8.2",
"description": "Local, metadata-only telemetry for Claude Code. A bundled observer records session, tool, and subagent lifecycle events into SQLite on your machine, an optional statusline shows live context and usage, and an OpenTelemetry Collector forwards redacted signals to the observer. Logs reach configured sinks, including PostHog, through the observer's consent-filtered outbox; traces and metrics use separate Collector sink pipelines for Grafana or generic OTLP. Telemetry payloads exclude prompts, responses, code, tool inputs and results, credentials, and environment values. Exporter settings you provide, including OTLP headers or tokens, are stored locally in %LOCALAPPDATA%\\Eigenwise\\Workbench\\observability.json on Windows, or ~/.local/share/Eigenwise/Workbench/observability.json when LOCALAPPDATA is not set, so an exporter can authenticate. Every sink beyond local SQLite is opt-in.",
"author": {
"name": "Eigenwise",
"email": "[email protected]"
},
"homepage": "https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/observability",
"repository": "https://github.com/Eigenwise/eigenwise-toolshed",
"license": "MIT",
"suiteTimeout": 300000,
"keywords": [
"observability",
"telemetry",
"opentelemetry",
"grafana",
"statusline",
"metrics",
"tokens",
"cost"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 33 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 12d ago Changed 202e2641c01c
- 15d ago Changed 76ad13d39e3a
- 17d ago Changed 00fd4b20fd66
- 23d ago Changed 17eb844db251
- 1mo ago Changed e2854f164375
- 1mo ago Changed bc70b665b073
- 1mo ago Changed d09c86b789f7
- 1mo ago Changed e388922f1b2a
- 1mo ago Changed d8c38623417f
- 1mo ago First seen · 24 lines scan A ea1aee882ae3
observability is a plugin published in the GitHub repository Eigenwise/eigenwise-toolshed (280 stars, last pushed 2d 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
api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.
csrf-protection
Implements CSRF protection using synchronizer tokens, double-submit cookies, and SameSite attributes. Use when securing web forms, protecting state-changing endpoints, or implementing defense-in-depth authentication.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
cloudflare-sandbox
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge. Use for untrusted code, Python/Node.js scripts, AI code interpreters, git operations.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
handbook-discover
Discover and audit all plugins in a Claude Code marketplace with installation status, versions, and component breakdown.