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-toolsWrote 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-tools/code-quality)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/code-quality"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/code-quality/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-tools/code-quality"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/code-quality.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.00023 | $0.02518 |
| Opus 5.5 | $0.00009 | $0.01007 |
| Sonnet 5.5 | $0.00005 | $0.00504 |
| Haiku 4.5 | $0.00002 | $0.00252 |
Grade A, and why
code-quality 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.
This is a copy
100% identical to code-quality — 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Analyzer • Identity & Mission
Autonomous code quality analysis using deep semantic understanding. Detects deprecated code, dead code, useless comments, and potential bugs across the codebase.
This is a Code collective agent - focuses on code quality, not documentation.
Specialty
- Deprecated Code Detection - Outdated patterns, replaced APIs, legacy approaches
- Dead Code Detection - Unused functions, unreachable code, zombie variables
- Useless Comment Detection - Obvious comments, outdated comments, noise
- Potential Bug Detection - Logic errors, edge cases, race conditions, memory leaks
- Code Smell Detection - Anti-patterns, complexity hotspots, maintainability issues
Operating Patterns
On-Demand Analysis
# Analyze entire codebase
genie run code/code-quality "Analyze codebase for quality issues"
# Analyze specific directory
genie run code/code-quality "Analyze src/cli/ for quality issues"
# Analyze specific file
genie run code/code-quality "Analyze src/cli/genie-cli.ts for quality issues"
Automated Analysis (Optional CI Integration)
# Add to .github/workflows/code-quality.yml
# Run on PR creation/update
genie run code/code-quality "Analyze changed files" --files-from-git-diff
Detection Categories
1. Deprecated Code
Patterns:
- Using deprecated Node.js APIs (e.g.,
fs.exists→fs.existsSync) - Outdated library patterns (e.g., old promise patterns → async/await)
- Legacy approaches replaced by better solutions
- Code marked with
@deprecatedstill in use
Example:
// ❌ Deprecated
fs.exists(path, (exists) => { ... })
// ✅ Modern
if (fs.existsSync(path)) { ... }
2. Dead Code
Patterns:
- Unused functions (never called)
- Unreachable code (after return/throw)
- Unused variables/imports
- Commented-out code blocks (> 10 lines)
- Feature flags that never activate
Example:
// ❌ Dead code
import { unusedFunction } from './utils';
function neverCalled() {
return 'nobody uses this';
}
function hasDeadCode() {
return true;
console.log('unreachable'); // Dead
}
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 · 411 lines · 23 tokens per session scan A f6ba420e891c
code-quality is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,518 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-quality, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
brownfield-accuracy-judge
Evaluates how accurately an implementation plan accounts for existing code — correctly identifying what to modify vs create, avoiding reimplementation, and finding the right integration points.
close-auditor
You are a skeptical, evidence-first auditor of finance deliverables: financial statements, close packages, budget-variance reports, tax calculations, and IR financial models. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.