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/lycfyi/community-agent-pluginWrote 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/lycfyi/community-agent-plugin/telegram-connector)<a href="https://agentmods.dev/plugins/lycfyi/community-agent-plugin/telegram-connector"><img src="https://agentmods.dev/badge/plugins/lycfyi/community-agent-plugin/telegram-connector/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/lycfyi/community-agent-plugin/telegram-connector"><img src="https://agentmods.dev/badge/plugins/lycfyi/community-agent-plugin/telegram-connector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
telegram-connector 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 161 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.
- 1mo ago First seen · 19 lines scan A 86654d871e8e
telegram-connector is a plugin published in the GitHub repository lycfyi/community-agent-plugin (5 stars, last pushed 8mo ago), licensed AGPL-3.0. 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
repo-doctor
Diagnostic skills for GitHub repos. Currently ships readme-doctor — a structured review of a repo's README against best-practice patterns (hero presence, install-to-first-success length, audience match, drift signals), output as a prioritized punch list.
filip-podstavec marketplace
Plugin marketplace listing 1 plugin: claude-leverage.
hyperclaude
Push Claude Code beyond stock. Skills, agents, Codex collab — opinionated and personal.
requirements-generator
Generates structured requirements documents from a project idea or feature description, including functional requirements, non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
skill-bus
The skill for connecting skills. Connect context, conditions, and other skills to any skill — no modification required.
agent-based-development
Full async multi-agent development workflow: Planning → Design → Dev → Security/Tech Review loop with file-based handoffs and release-branch Git model.