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/abs1294/fulin-claude-pluginsWrote 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/abs1294/fulin-claude-plugins/wtf)<a href="https://agentmods.dev/plugins/abs1294/fulin-claude-plugins/wtf"><img src="https://agentmods.dev/badge/plugins/abs1294/fulin-claude-plugins/wtf/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/abs1294/fulin-claude-plugins/wtf"><img src="https://agentmods.dev/badge/plugins/abs1294/fulin-claude-plugins/wtf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wtf 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 475 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.
- 3d ago Changed 5bef9dc6f1c9
- 5d ago Changed · +4 lines de5171f7e858
- 6d ago First seen · 24 lines scan A d43e1a45c100
wtf is a plugin published in the GitHub repository abs1294/fulin-claude-plugins (2 stars, last pushed yesterday), with no licence file. 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-06.
Other plugins, from other repositories
catchup
Async-team return-from-absence briefing. /catchup fans out to GitHub, git, Linear, and calendar, then emits one prioritized Context Brief instead of a firehose.
slack-workspace
The entire Slack Web API for Claude Code — 201 methods, approval-gated sending, a cached workspace reference, and scheduled-job alerting. Backed by the elnora-slack CLI.
visual-feedback
Turn any deliverable into ONE self-contained HTML review page with an inline comment pin on every element; collected feedback exports as markdown + JSON to paste back into the chat. English UI by default with an EN/DE toggle.
claude-code-monitor
Bring the iTerm window running Claude Code to the front the moment it needs your attention (macOS).
queue
End-of-Turn Queue — queue prompts with /queue:add and each is delivered back to Claude at the end of the turn, after it fully finishes its work, never mid-task. A FIFO prompt queue for Claude Code, built on a self-terminating Stop hook.
automate
Front desk for setting up automation in Claude Code — recurring loops, finish-line goals, and scheduled cloud routines. Picks the right native primitive (/goal, /loop, scheduled tasks, /schedule routines) and configures it safely with verifiable finish lines, turn caps, machine-vs-cloud placement, and tight routine…