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 brody-0125/my-claude-skills --skill plugin-introspectorgit 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/skills/brody-0125/my-claude-skills/plugin-introspector)<a href="https://agentmods.dev/skills/brody-0125/my-claude-skills/plugin-introspector"><img src="https://agentmods.dev/badge/skills/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/skills/brody-0125/my-claude-skills/plugin-introspector"><img src="https://agentmods.dev/badge/skills/brody-0125/my-claude-skills/plugin-introspector.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.00090 | $0.06832 |
| Opus 5.5 | $0.00036 | $0.02733 |
| Sonnet 5.5 | $0.00018 | $0.01366 |
| Haiku 4.5 | $0.00009 | $0.00683 |
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 2mo 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 — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Introspector — White-box Monitoring & Self-Improvement Meta-Plugin
A meta-plugin that monitors Claude Code workflow plugin execution at white-box level, collects execution data, and generates data-driven improvement proposals.
Role
A monitoring and analysis meta-plugin that provides end-to-end visibility into Claude Code workflow plugin execution. Collects tool traces, API interactions, token usage, and execution patterns via hooks. Provides analysis agents that identify bottlenecks, evaluate quality, detect anomalies, and generate concrete improvement proposals.
Terminology
- Plugin: An installable package (directory with
.claude-plugin/plugin.jsonandskills/) - Skill: An invocable unit within a plugin (directory with
SKILL.md) - Agent: A Task subagent definition (
.mdfile inagents/) - Proposal / Improvement: A concrete, ROI-scored change suggestion generated by
improve
Core Principles
- Data-driven improvement: Never guess — always base decisions on collected execution data
- Minimal overhead: Hook scripts must complete in <50ms, use append-only JSONL
- OTel compatibility: Trace data follows OpenTelemetry GenAI Semantic Conventions
- Tiered collection: Tier 0 (pure hooks) → Tier 1 (+ OTel Collector with native telemetry)
- Meta-rules compliance: All generated improvements must pass meta-rules validation
- Zero external dependencies: bash + jq only — no Python, no Node.js (Tier 1 adds optional otelcol-contrib)
Pre-Execution: Session Resolution
Before any command, resolve the session directory:
1. Run: ls -t ~/.claude/plugin-introspector/sessions/ | head -1
→ Gives the most recent session ID
2. If --session {id} was provided: use that ID instead
3. Set: SESSION_DIR = ~/.claude/plugin-introspector/sessions/{resolved-id}
4. Verify: stats.json exists in SESSION_DIR
5. If not found: display "No session data. Run a session with hooks enabled first."
Full details: resources/orchestration-protocol.md
What ships with it
44 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/anomaly-detector.md 3.7 KB
- agents/api-tracker.md 2.5 KB
- agents/auto-optimizer.md 2.3 KB
- agents/context-auditor.md 3.1 KB
- agents/improvement-generator.md 3.8 KB
- agents/plugin-profiler.md 2.4 KB
- agents/quality-evaluator.md 2.5 KB
- agents/quick-scanner.md 2.9 KB
- agents/security-auditor.md 3.8 KB
- agents/security-reporter.md 3.3 KB
- agents/token-optimizer.md 3.3 KB
- agents/workflow-analyzer.md 2.5 KB
- resources/ci-cd-integration.md 8.3 KB
- resources/data-schema.md 18 KB
- resources/docker-compose.otel.yml 3.8 KB
- resources/improvement-apply-protocol.md 3.3 KB
- resources/improvement-pipeline.md 7.3 KB
- resources/orchestration-protocol.md 24 KB
- resources/otel-collector-config.yaml 1.9 KB
- resources/otel-collector-guide.md 5.9 KB
- resources/security-patterns.md 7.9 KB
- resources/skill-activation-guide.md 2.5 KB
- resources/skills-map.md 4.0 KB
- scripts/_common.sh 13 KB runs code
- scripts/api-trace.sh 1.7 KB runs code
- scripts/dashboard.sh 6.5 KB runs code
- scripts/merge-otel-data.sh 6.1 KB runs code
- scripts/otel-config.yaml 1.5 KB
- scripts/otel-security-mapper.sh 9.9 KB runs code
- scripts/post-tool-trace.sh 3.7 KB runs code
- scripts/pre-tool-trace.sh 1.4 KB runs code
- scripts/rotate-data.sh 8.0 KB runs code
- scripts/security-baseline.sh 6.1 KB runs code
- scripts/security-check.sh 5.1 KB runs code
- scripts/security-dashboard.sh 10 KB runs code
- scripts/security-scan.sh 13 KB runs code
- scripts/session-end.sh 4.5 KB runs code
- scripts/session-start.sh 2.7 KB runs code
- scripts/session-stop.sh 3.6 KB runs code
- scripts/setup-otel-collector.sh 7.7 KB runs code
- scripts/skill-forced-eval-hook.sh 1.4 KB runs code
- scripts/subagent-trace.sh 2.6 KB runs code
- scripts/telemetry.sh 3.4 KB runs code
- scripts/tool-failure-trace.sh 2.2 KB runs code
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.
- 2mo ago First seen · 593 lines · 90 tokens per session scan A 1d0fb7e161f0
plugin-introspector is a skill published in the GitHub repository brody-0125/my-claude-skills (2 stars, last pushed 8mo ago), licensed MIT. It adds 90 tokens to every session and 6,832 once invoked, about $0.0004 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
brainstorming
Structured brainstorming for Symfony projects - explore requirements, identify components, and plan architecture collaboratively.
executing-plans
Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation.
using-symfony-superpowers
Entry point for Symfony Superpowers - lightweight workflow guidance and command map.
writing-plans
Create structured implementation plans for Symfony features with clear steps, dependencies, and acceptance criteria.
architect
Answer build-or-adopt honestly, then design one committed architecture from your own understanding of the problem — driven by ranked quality attributes, stress-tested against the field and against change, proven by a walking skeleton, its consequences confirmed by the user, committed to ARCHITECTURE.md. A command the…
designer
Settle the look before the pixels — audience and context first, then the base and the delta, directions drawn as tiles from a written brief and a critic's read of the chosen one, accessibility as the floor, one design language committed to DESIGN.md as tokens with roles. A command the user types, for work with an…