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 jeongph/claude-telemetrynpx agentmods add plugins/jeongph/claude-telemetry/marketplacegit clone --depth 1 https://github.com/jeongph/claude-telemetryWrote 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/jeongph/claude-telemetry/marketplace)<a href="https://agentmods.dev/plugins/jeongph/claude-telemetry/marketplace"><img src="https://agentmods.dev/badge/plugins/jeongph/claude-telemetry/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jeongph-claude-telemetry marketplace 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 4d 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": "jeongph-claude-telemetry",
"owner": {
"name": "JeongUk Park",
"email": "[email protected]"
},
"description": "Marketplace for claude-telemetry",
"plugins": [
{
"name": "claude-telemetry",
"source": {
"source": "url",
"url": "https://github.com/jeongph/claude-telemetry.git",
"sha": "cfd42633ece0f5f5e06091da51d6810f7f7e676b"
},
"description": "Customizable multi-line status line for Claude Code — real-time session telemetry in your terminal",
"version": "2.6.0"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 21 lines scan A e57fd749ef72
jeongph-claude-telemetry marketplace is a plugin published in the GitHub repository jeongph/claude-telemetry (5 stars, last pushed 1mo 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
deploy-pilot
Deployment automation with Dockerfile generation, CI/CD pipelines, and infrastructure as code.
a11y-audit
Full accessibility audit with WCAG compliance checking.
analytics-reporter
Generate analytics reports and dashboard configurations from project data.
aws-helper
AWS service configuration and deployment automation.
azure-helper
Azure service configuration and deployment automation.
backend-architect
Backend service architecture design with endpoint scaffolding.