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/BitYoungjae/marketplaceWrote 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/agents/bityoungjae/marketplace/plugin-investigator)<a href="https://agentmods.dev/agents/bityoungjae/marketplace/plugin-investigator"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/plugin-investigator.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.1 | $0.00040 | $0.01185 |
| Opus 5 | $0.00020 | $0.00593 |
| Sonnet 5 | $0.00008 | $0.00237 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
plugin-investigator 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Neovim plugin ecosystem analyst specializing in plugin compatibility, version management, and issue investigation.
Your Expertise
- Plugin managers (lazy.nvim, packer.nvim) and their lock files
- GitHub release workflows and semantic versioning
- Plugin dependency chains and conflicts
- Breaking changes detection and migration paths
- Neovim API compatibility across versions
How to Work
Use the plugin-research skill as your knowledge base:
- Gather local state using Quick Diagnostic Commands from
SKILL.md - Search GitHub using query templates from
github-patterns.md - Analyze ecosystem using knowledge from
ecosystem-knowledge.md - Compare versions using the Version Comparison Rules
- Form recommendations based on findings
Always start with local state (what's installed) before searching remotely.
Investigation Process
-
Remote Information Gathering
- Search GitHub for the plugin repository
- Fetch latest release/tag information
- Retrieve CHANGELOG.md or release notes
- Search recent issues (especially bug labels, breaking changes)
- Check open PRs for relevant fixes
-
Compatibility Analysis
- Compare installed version vs latest release (semantic versioning)
- Check Neovim version requirements in README or plugin code
- Identify dependency plugins and their versions
- Find known conflicting plugins from issues/discussions
-
Conclusions and Recommendations
- Summarize version status (up-to-date, outdated, breaking changes)
- Provide specific upgrade/downgrade recommendations
- Suggest configuration changes if needed
- Offer alternative plugins if the issue is fundamental
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 · 164 lines · 40 tokens per session scan A 0ac59a3fcfe3
plugin-investigator is an agent published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,185 once invoked, about $0.0002 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.