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/plastic-labs/cursor-honchoWrote 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/plastic-labs/cursor-honcho/honcho-dev)<a href="https://agentmods.dev/plugins/plastic-labs/cursor-honcho/honcho-dev"><img src="https://agentmods.dev/badge/plugins/plastic-labs/cursor-honcho/honcho-dev/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/plastic-labs/cursor-honcho/honcho-dev"><img src="https://agentmods.dev/badge/plugins/plastic-labs/cursor-honcho/honcho-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
honcho-dev 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 21d 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": "honcho-dev",
"displayName": "Honcho SDK Tools",
"version": "0.1.0",
"description": "Skills for building AI applications with the Honcho SDK",
"author": {
"name": "Plastic Labs",
"email": "[email protected]"
},
"homepage": "https://honcho.dev",
"repository": "https://github.com/plastic-labs/cursor-honcho",
"license": "MIT",
"keywords": ["sdk", "development", "migration", "honcho"],
"logo": "assets/logo.svg"
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 186 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.
- 21d ago First seen · 16 lines scan A 78440840a983
honcho-dev is a plugin published in the GitHub repository plastic-labs/cursor-honcho (7 stars, last pushed 21d 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-10-21.
honcho-dev compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| honcho-devplastic-labs/cursor-honcho | Plugin | 7 | 21d ago | MIT | A | — | Cursor |
| clip-aware-embeddingscuriositech/some_claude_skills | Plugin | 265 | 6d ago | MIT | A | — | Claude Code |
| tao-skill-bankNVIDIA-TAO/tao-skill-bank | Plugin | 100 | today | Apache-2.0 | A | — | Claude Code |
| classifiercardmagic/classifier | Plugin | 741 | 4d ago | none | A | — | Claude Code |
| databricksdatabricks/databricks-agent-skills | Plugin | 394 | yesterday | none | A | — | Claude Code, Cursor |
| twelvelabstwelvelabs-io/twelve-labs-claude-code-plugin | Plugin | 26 | 1mo ago | MIT | A | — | Claude Code |
| sql-database-pipelinedlt-hub/dlthub-ai-harness | Plugin | 65 | yesterday | none | A | — | Claude Code |