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 TNT-Likely/honeycombnpx agentmods add plugins/tnt-likely/honeycomb/beecount-releasegit clone --depth 1 https://github.com/TNT-Likely/honeycombGrade A, and why
beecount-release 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 2d 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": "beecount-release",
"description": "BeeCount 全家桶发版流水线:双仓 tag 触发 CI、changelog 双格式、官网同步、视频文案收尾,带版本号与发布范围的用户确认门。",
"version": "0.1.1",
"author": {
"name": "sunxiao",
"email": "[email protected]",
"url": "https://github.com/TNT-Likely"
},
"homepage": "https://github.com/TNT-Likely/honeycomb/tree/main/plugins/beecount-release",
"repository": "https://github.com/TNT-Likely/honeycomb",
"license": "MIT",
"keywords": [
"release",
"beecount",
"changelog",
"workflow",
"ci"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 176 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.
- 2d ago First seen · 21 lines scan A 481c8c9707c7
beecount-release is a plugin published in the GitHub repository TNT-Likely/honeycomb (2 stars, last pushed 2mo 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
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
backend-architecture
Small, opinionated architecture guide for production backend services across languages and frameworks.
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.
esp32-cpp
Evidence-first ESP32 firmware guidance for hardware, FreeRTOS, memory, peripherals, and field failures.
maestro-mobile-validator
iOS and Android mobile app validation via Maestro flows with simulator management and CI patterns.
peekaboo-macos-validator
Runtime observation, interaction, and visual critique for native macOS interfaces via Peekaboo.