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/brody-0125/my-claude-skillsWrote 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/brody-0125/my-claude-skills/plugin-introspector)<a href="https://agentmods.dev/plugins/brody-0125/my-claude-skills/plugin-introspector"><img src="https://agentmods.dev/badge/plugins/brody-0125/my-claude-skills/plugin-introspector/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/brody-0125/my-claude-skills/plugin-introspector"><img src="https://agentmods.dev/badge/plugins/brody-0125/my-claude-skills/plugin-introspector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
plugin-introspector 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "plugin-introspector",
"description": "White-box monitoring and self-improvement meta-plugin for Claude Code workflow plugins",
"version": "1.0.0",
"hooks": {
"SessionStart": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "PI_S=\"${INTROSPECTOR_SCRIPTS:-${CLAUDE_PROJECT_DIR:-.}/plugins/plugin-introspector/skills/plugin-introspector/scripts}\"; bash \"$PI_S/session-start.sh\" 2>/dev/null || true"
}
]
}
],
"PreToolUse": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "PI_S=\"${INTROSPECTOR_SCRIPTS:-${CLAUDE_PROJECT_DIR:-.}/plugins/plugin-introspector/skills/plugin-introspector/scripts}\"; if [ \"${PI_ENABLE_SECURITY:-0}\" = \"1\" ]; then bash \"$PI_S/security-check.sh\" 2>/dev/null; fi"
},
{
"type": "command",
"command": "PI_S=\"${INTROSPECTOR_SCRIPTS:-${CLAUDE_PROJECT_DIR:-.}/plugins/plugin-introspector/skills/plugin-introspector/scripts}\"; bash \"$PI_S/pre-tool-trace.sh\" 2>/dev/null || true"
}
]
}
],
"PostToolUse": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "PI_S=\"${INTROSPECTOR_SCRIPTS:-${CLAUDE_PROJECT_DIR:-.}/plugins/plugin-introspector/skills/plugin-introspector/scripts}\"; bash \"$PI_S/post-tool-trace.sh\" 2>/dev/null || true"
}
]
}
],
"PostToolUseFailure": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "PI_S=\"${INTROSPECTOR_SCRIPTS:-${CLAUDE_PROJECT_DIR:-.}/plugins/plugin-introspector/skills/plugin-introspector/scripts}\"; bash \"$PI_S/tool-failure-trace.sh\" 2>/dev/null || true"
}
]
}
],
"Notification": [
{
"matcher": "",
"hooks": [
{
"typeWhat it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 174 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.
- 8d ago First seen · 100 lines scan A fd7a279d7723
plugin-introspector is a plugin published in the GitHub repository brody-0125/my-claude-skills (2 stars, last pushed 6mo 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
task
Chat-first task workflow: grill the plan one question at a time, then capture the discussion at the depth you pick — to-task / to-plan / to-roadmap / to-spec, never a flag — into a Markdown artifact under .task/. No execution skill — any session told to implement the artifact follows its stamped Execution block to a…
workinggenius
A development workflow that walks every piece of work through the six Working Geniuses — Wonder, Invention, Discernment, Galvanizing, Enablement, Tenacity — every stage a command the user types, every checkpoint a live exchange.
simple-statusline-marketplace
A minimal statusline for Claude Code.
simple-statusline
A simple, hackable two-line statusline for Claude Code showing model, git status, context usage, and rate limits.
csw
Ship a tracker ticket: dispatch it into a worktree, drive it to a pull request, merge it after review, and clean up after itself.
cprof
Select which Claude account a session uses, by default profile, per-repo pin, or directory rule.