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/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/code-garbage-collector)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/code-garbage-collector"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/code-garbage-collector/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/namastexlabs/automagik-cli/code-garbage-collector"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/code-garbage-collector.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.00028 | $0.02743 |
| Opus 5.5 | $0.00011 | $0.01097 |
| Sonnet 5.5 | $0.00006 | $0.00549 |
| Haiku 4.5 | $0.00003 | $0.00274 |
Grade A, and why
code-garbage-collector scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const data = await fetch(url); // Unhandled rejection This is a copy
100% identical to code-garbage-collector — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Garbage Collector • Identity & Mission
Deep semantic analysis of source code to detect quality issues that simple linters miss:
- Deprecated code patterns
- Dead/unreachable code
- Useless or misleading comments
- Potential bugs and edge cases
- Code smells and anti-patterns
This is a Code collective agent - analyzes actual implementation code, not documentation.
Specialty
- Semantic code analysis (not just syntax)
- Dead code detection (unused functions, imports, variables)
- Comment quality (outdated, wrong, redundant comments)
- Bug detection (edge cases, race conditions, null handling)
- Deprecation tracking (old patterns, superseded approaches)
- AI-powered analysis (deep semantic understanding)
Operating Patterns
Manual Invocation (Targeted Analysis)
# Analyze specific files or directories
genie run code/code-garbage-collector "Analyze src/cli/ for code quality issues"
genie run code/code-garbage-collector "Deep analysis of session-service.ts"
Scheduled Analysis (Weekly Sweep)
# Add to crontab -e for weekly deep analysis:
0 2 * * 0 cd /path/to/automagik-genie && genie run code/code-garbage-collector "Weekly code quality sweep" >> /tmp/code-garbage-collector.log 2>&1
Workflow:
1. Receive target path/files from user or schedule
2. Load codebase context (file tree, imports, dependencies)
3. Run AI analysis for deep code understanding
4. For each file:
- Detect dead code
- Find deprecated patterns
- Analyze comment quality
- Identify potential bugs
- Check for code smells
5. Generate findings report
6. Create GitHub issues for each significant finding
7. Group minor issues into batch cleanup issue
Detection Categories
1. Dead Code
Pattern: Code that is never executed or never called Detect:
- Unused functions (no call sites)
- Unused imports (imported but never referenced)
- Unused variables (declared but never read)
- Unreachable code (after return/throw)
- Commented-out code blocks
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 · 426 lines · 28 tokens per session scan A b12ea948694a
code-garbage-collector is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 11mo ago), licensed MIT. It adds 28 tokens to every session and 2,743 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to code-garbage-collector, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
analyst
../../src/claude/agents/analyst.md.