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-quality)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/code-quality"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/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-cli/code-quality"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/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 | $0.00012 | $0.01259 |
| Sonnet 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 5d 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.
- 5d ago First seen · 411 lines · 23 tokens per session scan A f6ba420e891c
code-quality is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It adds 23 tokens to every session and 2,518 once invoked, about $0.0001 per session on Opus 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
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues. Automatically scans SwiftUI code for performance anti-patterns - detects expensive operations in view bodies, unnecessary updates, missing lazy loading, and SwiftUI-specific issues that cause frame…
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
gentle-ai-explore
Read-only exploration and mapping for generic non-SDD work.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
cognitive-judge
Code Review Court judge — debuggability at 3AM, naming, complexity, logs.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.