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 skills add iBrain-BVBA/gutt-claude-code-plugin --skill skill_namegit 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/skills/ibrain-bvba/gutt-claude-code-plugin/skill_name)<a href="https://agentmods.dev/skills/ibrain-bvba/gutt-claude-code-plugin/skill_name"><img src="https://agentmods.dev/badge/skills/ibrain-bvba/gutt-claude-code-plugin/skill_name/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/skills/ibrain-bvba/gutt-claude-code-plugin/skill_name"><img src="https://agentmods.dev/badge/skills/ibrain-bvba/gutt-claude-code-plugin/skill_name.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00072 | $0.01488 |
| Opus 5.5 | $0.00029 | $0.00595 |
| Sonnet 5.5 | $0.00014 | $0.00298 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
SKILL_NAME 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{SKILL_TITLE}}
{{ONE_PARAGRAPH_ON_WHAT_THIS_SKILL_DOES_AND_WHAT_IT_HANDS_BACK}}.
SCAFFOLD NOTE — delete this paragraph and every other one marked the same way; they are
addressed to you rather than to the workflow that will read this skill, and the review step
fails while any remain. Rename this directory and the name: above together: a skill's
name: must equal its directory name, and nothing at runtime reports a mismatch.
Underneath, memory-search owns the search ladder and the relevance gate, graph-traversal
owns relationship walking, and memory-capture owns any durable write. This skill adds only
what is specific to {{THE_ROLE_ACTIVITY}} — the inputs to read, the order to read them in, and
the shape of the output. Do not restate their rules here. A second copy of the search
ladder is a copy that drifts, and the reader cannot tell which one is current.
Memory identity
This named workflow writes to the org graph as
{{SKILL_NAME}}--<scope>. Resolve the authoritative group first.
Resolve <scope> at runtime, where you run: the scope bound to this working
directory (the invoked agent-memory-protocol skill carries the file read), else
the git remote's owner/repo, else the working folder's name — lower-cased, with
every run of characters outside a-z0-9 collapsed to a single dash and the dashes
trimmed. A memory group id is never a scope: identity is already keyed on the group,
so a scope taken from it separates nothing. Never register the base name alone:
registration merges on name + group, so a bare name joins whatever else registered
under it, and org writes cannot be reassigned afterwards.
Then register before the first identity-scoped recall or tagged write:
register_agent(
name="{{SKILL_NAME}}--<scope>",
description="{{WHAT_THIS_SKILL_DOES_IN_A_SENTENCE_OR_TWO}}",
group_id=<the resolved org group>)
Keep the returned node id or uuid for verification. A read-only or personal-only path declares no memory identity instead: remove this metadata and section, skip registration and scoped recall, and never tag personal writes.
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 · +49 lines eb9448a508d0
- 1mo ago First seen · 91 lines · 72 tokens per session scan A 1dc52dfbb9b9
SKILL_NAME is a skill published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,488 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…