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/iBrain-BVBA/gutt-claude-code-pluginWrote 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/ibrain-bvba/gutt-claude-code-plugin/gutt-developer)<a href="https://agentmods.dev/plugins/ibrain-bvba/gutt-claude-code-plugin/gutt-developer"><img src="https://agentmods.dev/badge/plugins/ibrain-bvba/gutt-claude-code-plugin/gutt-developer/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/ibrain-bvba/gutt-claude-code-plugin/gutt-developer"><img src="https://agentmods.dev/badge/plugins/ibrain-bvba/gutt-claude-code-plugin/gutt-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gutt-developer 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": "gutt-developer",
"version": "0.3.0",
"dependencies": ["gutt-pro"],
"defaultEnabled": true,
"author": {
"name": "iBRAIN BV",
"email": "[email protected]"
},
"description": "Developer skills for Jira tickets and pull requests — context research, duplicates, estimates, bug triage, story breakdown, and memory-informed review — backed by GUTT organizational memory",
"homepage": "https://gutt.pro",
"repository": "https://github.com/iBrain-BVBA/gutt-claude-code-plugin",
"license": "MIT",
"keywords": [
"developer",
"jira",
"ticket-research",
"estimation",
"bug-triage",
"code-review",
"organizational-memory",
"gutt"
]
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 715 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 Changed be5c89a05a15
- 1mo ago Changed ce0d704d364c
- 1mo ago First seen · 25 lines scan A f13c278eecd2
gutt-developer is a plugin published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo 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
han-linear
Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.
ring-pm-team
Pre-dev planning workflows: 4-gate and 8-gate orchestrators for PRD, TRD, OpenAPI contracts, schema design, and a phased plan. 14 skills + 4 research agents.
magpie-pr-management
Apache Magpie — PR-queue management: triage, stats, deep code review, stack review, quick-merge, stale-sweep, reviewer routing, pre-first-PR checks.
nid-team
NI&D team PR triage and review workflow tools.
project-overview
Generates a deterministic cross-project status map from registered projects' session handoffs.
lets
Development workflow with session management, code review, and task tracking.