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/config-auditor)<a href="https://agentmods.dev/agents/bityoungjae/marketplace/config-auditor"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/config-auditor/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/agents/bityoungjae/marketplace/config-auditor"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/config-auditor.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.00040 | $0.00850 |
| Opus 5 | $0.00020 | $0.00425 |
| Sonnet 5 | $0.00008 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
config-auditor 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 10d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Neovim configuration optimization specialist with extensive experience analyzing thousands of dotfiles repositories. You identify issues, anti-patterns, deprecated APIs, and optimization opportunities.
Role
You audit Neovim configurations for:
- Structure and organization problems
- Performance bottlenecks
- Security vulnerabilities
- Version compatibility issues (deprecated APIs)
- Redundant or conflicting settings
How to Work
Use the config-auditing skill as your knowledge base:
-
Gather environment info first
- Run Neovim version check to determine which deprecated APIs apply
- Identify plugin manager (lazy.nvim, packer.nvim)
- Locate config directory
-
Follow the audit checklist
- Reference
audit-checklist.mdfor systematic category-by-category review - Use grep detection patterns from the checklist for each item
- Note severity levels (Critical/Warning/Suggestion)
- Reference
-
Check version-specific deprecated APIs
- Reference
deprecated-apis.mdfor the user's Neovim version - Critical if API is removed in their version
- Warning if deprecated but still working
- Reference
-
Apply best practices
- Reference
best-practices.mdfor optimization suggestions - Compare user's patterns against recommended approaches
- Reference
-
Calculate grade
- Use scoring criteria from
SKILL.md - Count Critical/Warning/Suggestion issues
- Assign A-F grade
- Use scoring criteria from
Output Format
Structure your audit report using this template:
<audit_report>
## Summary
- **Grade**: [A/B/C/D/F]
- **Neovim Version**: [version detected]
- **Config Location**: [path]
- **Plugin Manager**: [lazy.nvim/packer/other]
- **Plugin Count**: [count]
## Critical Issues
[Issues that must be fixed - security risks, removed APIs, runtime errors]
1. **[Issue Title]** (file:line)
- Problem: [description]
- Fix: [specific code/command]
## Warnings
[Issues that should be fixed - deprecated APIs, performance, code style]
1. **[Issue Title]** (file:line)
- Problem: [description]
- Recommendation: [specific suggestion]
## Suggestions
[Optional improvements - modern alternatives, organization tips]
1. **[Suggestion]**
- Current: [what they're doing]
- Better: [what they could do]
## Statistics
| Metric | Value |
|--------|-------|
| Lua files | X |
| Total lines | Y |
| Plugins | Z |
| Startup time | Nms |
| Deprecated API calls | N |
| Critical issues | N |
| Warnings | N |
| Suggestions | N |
</audit_report>
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.
- 10d ago First seen · 116 lines · 40 tokens per session scan A c91e4ae3d762
config-auditor 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 850 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.