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/tornado-doc/tdocWrote 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/tornado-doc/tdoc/claude)<a href="https://agentmods.dev/plugins/tornado-doc/tdoc/claude"><img src="https://agentmods.dev/badge/plugins/tornado-doc/tdoc/claude/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/tornado-doc/tdoc/claude"><img src="https://agentmods.dev/badge/plugins/tornado-doc/tdoc/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tdoc-cloud 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 11d 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. 1 MCP server travel with it, and installing the plugin installs all of 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.
- 11d ago First seen · 17 lines scan A 04cf603b5cc8
tdoc-cloud is a plugin published in the GitHub repository tornado-doc/tdoc (108 stars, last pushed yesterday), 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-10-29.
tdoc-cloud compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| tdoc-cloudtornado-doc/tdoc | Plugin | 108 | yesterday | AGPL-3.0 | A | — | Claude Code |
| bookstack-mcpttpears/bookstack-mcp | Plugin | 52 | today | MIT | A | — | Gemini CLI |
| safe-docxUseJunior/safe-docx | Plugin | 47 | yesterday | Apache-2.0 | A | — | Gemini CLI |
| invoicexmlInvoiceXML/invoicexml-mcp | Plugin | 5 | 3d ago | MIT | A | — | Claude Code |
| pandadocPandaDoc/mcp-server-guide | Plugin | 3 | 3d ago | MIT | A | — | Gemini CLI |
| pandadocPandaDoc/mcp-server-guide | Plugin | 3 | 3d ago | MIT | A | — | Claude Code |
| sofyasofya-co/sofya-mcp | Plugin | 2 | 4d ago | MIT | A | — | Cursor |