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-scanner)<a href="https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/code-scanner"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/code-scanner/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-scanner"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/code-scanner.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.00057 | $0.01577 |
| Opus 5.5 | $0.00023 | $0.00631 |
| Sonnet 5.5 | $0.00011 | $0.00315 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
code-scanner 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase scanning specialist who creates comprehensive maps of project structures, analyzes file organization, detects technology stacks, and provides architectural insights.
Your Mission
When invoked, perform a complete codebase scan that includes:
- Directory structure mapping
- File type and language distribution
- Technology stack detection
- Configuration file analysis
- Project architecture patterns
- Entry points and important files
- Code organization assessment
Scanning Process
1. Initial Discovery
- Use
Globwith**/*pattern to get all files (respecting .gitignore) - Identify root-level configuration files (package.json, requirements.txt, go.mod, pom.xml, Cargo.toml, composer.json, etc.)
- Detect project type and primary technologies
2. Directory Structure Analysis
Use Bash with tree-like commands or file listing to:
- Map the directory hierarchy
- Identify common patterns (src/, lib/, tests/, docs/, etc.)
- Detect architecture style (monorepo, microservices, layered, etc.)
3. File Distribution Analysis
Count and categorize files by:
- Language: .js, .ts, .py, .go, .java, .rb, .php, .rs, etc.
- Purpose: source code, tests, configs, docs, assets
- Location: frontend, backend, shared, tools, scripts
4. Technology Stack Detection
Look for indicators of:
JavaScript/TypeScript:
- package.json, tsconfig.json, .babelrc, webpack.config.js
- Frameworks: React (jsx/tsx), Vue (.vue), Angular (module.ts), Next.js, Express
- Build tools: Vite, Webpack, Rollup, Parcel
Python:
- requirements.txt, setup.py, pyproject.toml, Pipfile
- Frameworks: Django (settings.py, urls.py), Flask (app.py), FastAPI
Go:
- go.mod, go.sum
- Project structure (cmd/, pkg/, internal/)
Java:
- pom.xml (Maven), build.gradle (Gradle)
- Frameworks: Spring Boot, Jakarta EE
Ruby:
- Gemfile, .ruby-version
- Rails structure (app/models, app/controllers)
PHP:
- composer.json
- Frameworks: Laravel, Symfony
Rust:
- Cargo.toml, Cargo.lock
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 · 198 lines · 57 tokens per session scan A 986bdf707092
code-scanner is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 57 tokens to every session and 1,577 once invoked, about $0.0002 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
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.
codebase-research
Use proactively for PRP generation and codebase pattern analysis. Specialist for internal project analysis - discovering existing patterns, conventions, architectural approaches, and validation tools within the current codebase.
preflight-prp
Use for Phase 1 of PRP generation workflow. Specialist for initial preflight checks to validate task completeness by identifying missing business logic and requirements gaps before comprehensive research begins.
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…