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/Green-PT/honey-for-devsWrote 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/green-pt/honey-for-devs/gemini-extension)<a href="https://agentmods.dev/plugins/green-pt/honey-for-devs/gemini-extension"><img src="https://agentmods.dev/badge/plugins/green-pt/honey-for-devs/gemini-extension/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/green-pt/honey-for-devs/gemini-extension"><img src="https://agentmods.dev/badge/plugins/green-pt/honey-for-devs/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
honey 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 3d 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": "honey",
"version": "1.1.0",
"description": "Honey (I Shrunk the AI) — write less code and say less about it.",
"contextFileName": "AGENTS.md"
}
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.
- 3d ago First seen · 7 lines scan A c0f9cb219049
honey is a plugin published in the GitHub repository Green-PT/honey-for-devs (295 stars, last pushed 4d 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-09-08.
Other plugins, from other repositories
developer-essentials
Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management.
albino
Personal productivity plugin: brings Rashad's workflows to Claude Code.
fasterizy
Speed up agent planning, discussion, and docs without losing technical effectiveness. Code stays unchanged.
change-management
Stakeholder impact mapping, change readiness assessment, sponsor roadmaps, communications planning, and resistance diagnosis — the people side of transformation, separate from program governance and operating model design.
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
data-validation-suite
Schema validation, data quality monitoring, streaming validation pipelines, and input validation for backend APIs.