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.
npx agentmods add instructions/ibrain-bvba/gutt-claude-code-plugin/claude-mdgit 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/instructions/ibrain-bvba/gutt-claude-code-plugin/claude-md)<a href="https://agentmods.dev/instructions/ibrain-bvba/gutt-claude-code-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/ibrain-bvba/gutt-claude-code-plugin/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.03620 | $0.03620 |
| Opus 5 | $0.01810 | $0.01810 |
| Sonnet 5 | $0.00724 | $0.00724 |
| Haiku 4.5 | $0.00362 | $0.00362 |
Grade A, and why
gutt-claude-code-plugin CLAUDE.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gutt Claude Code Plugin
Project Overview
This is a Claude Code plugin that integrates gutt (Graph-based Unified Thinking Tool) memory capabilities into Claude Code workflows. The plugin provides:
- Memory Integration: Connect Claude Code to gutt's knowledge graph for persistent organizational memory
- Skills & Hooks: Custom skills and hooks for enhanced agent workflows
- MCP Tools: Additional MCP server configurations for extended capabilities
Architecture
gutt-plugins/ # marketplace repo (root is NOT a plugin)
├── .claude-plugin/ # marketplace.json — lists gutt-core + gutt-mentor + gutt-developer + gutt-product
├── gutt-core/ # core plugin (name + displayName: gutt-pro; dir name kept)
│ ├── .claude-plugin/ # plugin.json
│ ├── hooks/ # Claude Code hooks (.cjs); hooks/lib/* are real files, owned here
│ ├── skills/ agents/ commands/
│ └── rules/ mcp.json config.json.example
├── gutt-mentor/ # mentor plugin (depends on gutt-pro) — onboarding + mentor agents, personal-scope program design/tracking
├── gutt-developer/ # developer plugin (depends on gutt-pro) — ticket research/duplicates/estimate, bug-investigation, sub-task-breakdown, pr-re-review + pr-reviewer & bug-investigator agents; no hooks
├── gutt-product/ # product plugin (depends on gutt-pro) — story-creation, backlog-dedupe, backlog-prioritization for product leadership; no hooks
├── .claude/ # repo-dev tooling (agents, commands, settings) — not shipped
├── templates/ # role-plugin scaffold + its review gates — not shipped
├── tests/ # Unit and E2E tests
├── evals/ # prompt/skill bench — not shipped; free half gated (see below)
├── docs/ # Documentation and assets
└── package.json
The plugin is gutt-pro; its directory is gutt-core/. GP-931 renamed the plugin
(name and displayName) and deliberately left the directory alone — renaming it would
re-point the marketplace source for no user-visible gain. So gutt-core/ is a path and
gutt-pro is an identity, and they do not match on purpose. The GitHub repository keeps
its own name too
(gutt-claude-code-plugin), which is why that string still appears in repository URLs and
in filesystem paths derived from this checkout. Anywhere else it is a stale reference.
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.
- 4d ago First seen · 266 lines · 3,620 tokens per session scan A 1d5f241ab3d3
gutt-claude-code-plugin CLAUDE.md is an instructions file published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 2d ago), licensed MIT. It adds 3,620 tokens to every session, about $0.0181 per session on Opus 5. 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.