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 skills/ibrain-bvba/gutt-claude-code-plugin/skill_namenpx 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.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.00072 | $0.00961 |
| Opus 5 | $0.00036 | $0.00481 |
| Sonnet 5 | $0.00014 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
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 5d 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 — 91 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 agent 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.
Hard rules (non-negotiable — read first)
- The ticket tracker and its wiki are the system of record. Read the ticket and its linked pages before memory, and report against them. Never propose tracker mechanics this organization does not use — the label, template, and milestone conventions a public repository runs on do not transfer to closed delivery work.
- Produce input, never a committed number or a written field. {{WHAT_THIS_SKILL_OUTPUTS}} is a proposal for the team to argue with. Write nothing into the tracker, and post no comment, without approval of the exact text in the session.
- Cite every claim that rests on a record. A finding drawn from memory or from a page quotes and names its source. An uncited claim presented as the team's standard cannot be argued with by the person it is aimed at.
- Engagement scope on every write. Pass the group explicitly. Client work does not cross tenants: nothing learned on one engagement is written into another's scope, and nothing client-identifying goes into a shared or personal scope.
- Say what was not found. An empty recall is a result. Report it rather than filling the gap with a plausible-sounding inference.
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.
- 5d 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 2d ago), licensed MIT. It adds 72 tokens to every session and 961 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…