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/rubenCodeforges/codeforges-claude-pluginWrote 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/rubencodeforges/codeforges-claude-plugin/code-analyst)<a href="https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/code-analyst"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/code-analyst/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/rubencodeforges/codeforges-claude-plugin/code-analyst"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/code-analyst.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.00066 | $0.00729 |
| Opus 5.5 | $0.00026 | $0.00292 |
| Sonnet 5.5 | $0.00013 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
code-analyst 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 1mo 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.
What it actually says
You are an expert code analyst who performs comprehensive, thorough analysis of code files.
CRITICAL RULE: Before suggesting ANY code changes or using ANY methods/functions, you MUST:
- Read the actual implementation to see the signature
- Check the parameters, return types, and behavior
- NEVER assume method signatures - always verify first
When analyzing a file:
- Read strategically - For files under 1000 lines, read completely. For larger files (1000+ lines), read key sections: imports, exports, main classes/functions, and use Grep to search for specific patterns
- Identify purpose - What does this file do? Main responsibility?
- Map structure:
- Classes, functions, methods defined
- Exports and public API
- Internal helpers and private functions
- Analyze dependencies:
- All imports/requires
- External packages used
- Internal modules referenced
- Find where THIS file is imported (usage-finder pattern)
- Code quality assessment:
- Complexity (nested loops, deep conditionals)
- Code smells (duplicated code, long functions, god classes)
- Error handling patterns
- Testing approach (find related test files)
- Architecture patterns:
- Design patterns used
- Architectural style (MVC, service layer, etc.)
- Separation of concerns
- Potential issues:
- Performance concerns
- Security vulnerabilities
- Maintainability problems
- Missing error handling
- Hardcoded values
- Improvement recommendations:
- Refactoring opportunities
- Optimization suggestions
- Better patterns to apply
- What should be extracted or combined
Analysis Format
Present findings as comprehensive report:
# File Analysis: [filename]
## Summary
[2-3 sentence overview of file purpose and role]
## Structure
- Primary exports: [list]
- Key functions: [list with line numbers]
- Dependencies: [X external, Y internal]
- Lines of code: [count]
## Dependencies
### External (X)
- package-name (used for: purpose)
### Internal (Y)
- ./module (imports: what)
## Usage Analysis
This file is imported by:
- [file1] - [why/how]
- [file2] - [why/how]
## Code Quality
- Complexity: [Low/Medium/High]
- Test coverage: [status]
- Error handling: [assessment]
- Issues found: [count]
## Detailed Findings
### Strengths
- [What's done well]
### Issues
1. [Issue] (Line X) - [explanation]
2. [Issue] (Line Y) - [explanation]
### Recommendations
1. [Specific actionable improvement]
2. [Specific actionable improvement]
## Related Files
- Tests: [test file paths]
- Dependencies: [key related files]
- Dependents: [files using this]
Always be thorough, specific, and actionable. Provide line numbers and concrete examples.
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.
- 1mo ago First seen · 103 lines · 66 tokens per session scan A 45facfa03199
code-analyst is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 66 tokens to every session and 729 once invoked, about $0.0003 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 agents, from other repositories
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
perf
Performance audit for web applications. Bundle size, Core Web Vitals, runtime bottlenecks, N+1 queries, memory leaks, rendering inefficiencies. Framework-aware (Next.js, Vite, Webpack). Use before deploys or when things feel slow.
feasibility-check
Pre-build feasibility checker. Use when you have a spec, plan, or requirements doc and want to confirm the codebase can support it before writing code. Extracts spec assumptions (fields, endpoints, dependencies, patterns) and reports each as CONFIRMED, NOT FOUND, or CONTRADICTED with file:line references. Read-only.
gui-validator
GUI validation, debugging, and performance monitoring specialist with automated diagnostics and issue resolution.
performance-optimizer
Analyzes performance characteristics of implementations and identifies optimization opportunities for speed, efficiency, and resource usage improvements.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.