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/github-issue-triagegit clone --depth 1 https://github.com/TNT-Likely/honeycombGrade A, and why
github-issue-triage 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 yesterday.
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": "github-issue-triage",
"displayName": "GitHub Issue Triage",
"version": "0.1.0",
"description": "GitHub issue 治理工具集,含两个互补技能:triage(全量 open issue 按 数据正确性>呼声>卖点相关度 四级分流、产出优先级文档、可 /schedule 定期巡检)与 analyze-issue(单条深度分析:是否真 bug / 要不要修 / 优先级 / 功能请求是否合理,bug 结合代码库验证根因)。脱胎于 BeeCount issue 治理实践。",
"author": {
"name": "sunxiao",
"email": "[email protected]",
"url": "https://github.com/TNT-Likely"
},
"homepage": "https://github.com/TNT-Likely/honeycomb/tree/main/plugins/github-issue-triage",
"repository": "https://github.com/TNT-Likely/honeycomb",
"license": "MIT",
"keywords": ["github", "issue", "triage", "backlog", "prioritization", "gh-cli", "schedule"]
}
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.
- yesterday First seen · 16 lines scan A 37c60c3e723b
github-issue-triage 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
wondelai-skills
Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 65 skills for product strategy, UX design, marketing, sales, motivation, conversion optimization, code quality, and systems architecture, plus 14 guided-journey metaskills that orchestrate them step by step.
netresearch-claude-code-marketplace
Curated Agentic Skills for AI coding agents — TYPO3, PHP, Go, Docker, Jira, security, and more. Platform-agnostic skills following the open Agent Skills specification.
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.
peekaboo-macos-validator
Runtime observation, interaction, and visual critique for native macOS interfaces via Peekaboo.
electron-playwright-validator
Electron app UI automation and validation via Playwright CDP.