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/TNT-Likely/honeycombWrote 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/tnt-likely/honeycomb/github-issue-triage)<a href="https://agentmods.dev/plugins/tnt-likely/honeycomb/github-issue-triage"><img src="https://agentmods.dev/badge/plugins/tnt-likely/honeycomb/github-issue-triage/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/tnt-likely/honeycomb/github-issue-triage"><img src="https://agentmods.dev/badge/plugins/tnt-likely/honeycomb/github-issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 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.
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 it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 390 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 · 16 lines scan A 37c60c3e723b
github-issue-triage is a plugin published in the GitHub repository TNT-Likely/honeycomb (2 stars, last pushed 8d 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
team-motivation
Team motivation and management skills including Daniel Pink's Autonomy, Mastery, Purpose (AMP) principles and Andy Grove's High Output Management (leverage, one-on-ones, OKRs, task-relevant maturity).
metaskills
Fourteen guided journeys that orchestrate the whole skill library step by step — create, improve, and grow a business, website, or app, plus improve code quality, remove technical debt, design code architecture, optimize a conversion flow, and optimize an existing codebase for speed and structure. Each metaskill…
product-strategy
Product strategy and innovation frameworks including Jobs to Be Done (Clayton Christensen) for customer discovery and product design, tactical negotiation skills (Chris Voss), willingness-to-pay pricing (Monetizing Innovation), and startup metrics (Lean Analytics).
systems-architecture
Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), High Performance Browser Networking (Ilya Grigorik), and Team Topologies (Skelton & Pais).
sales-influence
Sales, persuasion, and messaging skills including Cialdini's influence psychology, Aaron Ross's outbound sales methodology, Heath Brothers' sticky messaging, and Alex Hormozi's offer creation.
agent-dispatch
Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.