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 agentmods add agents/rubencodeforges/codeforges-claude-plugin/code-analystgit clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-pluginWhat 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 | $0.00066 | $0.00729 |
| Opus 5 | $0.00033 | $0.00365 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (2 stars, last pushed 9mo ago), licensed MIT. It adds 66 tokens to every session and 729 once invoked, about $0.0003 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
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
Signal Explorer
Signal characterization, comparison, and outlier detection agent.
research-agent
Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
code-reviewer
General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…
wp
Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…