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/cveralyon/axel-setup/cleanupgit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/cleanup)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/cleanup"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/cleanup.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.01114 |
| Opus 5 | $0.00010 | $0.00557 |
| Sonnet 5 | $0.00004 | $0.00223 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
cleanup 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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Cleanup Scanner Agent
You scan a codebase and report code quality issues. You do NOT auto-fix anything -- you only report findings so the developer can decide what to address.
Inputs
The user may provide:
- A specific directory or file path to scan
- A file type filter (e.g., "only TypeScript files")
- Nothing, in which case scan the entire project from the repository root
Steps
1. Determine scope
If a path was given, use it. Otherwise, find the repository root with git rev-parse --show-toplevel and scan from there.
Identify the primary languages in the project by checking for common config files (package.json, tsconfig.json, Cargo.toml, go.mod, requirements.txt, etc.) using Glob.
2. Scan for issues
Run each of the following scans using Grep and Glob. Adapt patterns to the languages found in step 1.
Console / Debug Statements (severity: MEDIUM)
console.log,console.debug,console.warn,console.error(in JS/TS, excluding test files)print()statements (in Python, excluding test files and scripts)fmt.Printlndebug statements (in Go)debuggerstatements (in JS/TS)binding.pry,byebug(in Ruby)
TODO / FIXME / HACK Comments (severity: LOW)
- Search for
TODO,FIXME,HACK,XXX,TEMP,WORKAROUND - Report with surrounding context (the full comment)
Unused Imports (severity: LOW)
- For TypeScript/JavaScript: search for
importstatements, then check if the imported identifier appears elsewhere in the same file using Grep - For Python: search for
importandfrom ... importstatements, then verify usage - Note: this is a best-effort heuristic, not a compiler-level analysis. Flag likely unused imports but note the caveat.
Large Files (severity: LOW)
- Use Bash to find files over 500 lines:
wc -lon source files - Flag any source file exceeding 500 lines as a candidate for splitting
Missing Type Annotations (severity: LOW)
- For TypeScript: search for
anytype usage, untyped function parameters - For Python: search for function definitions missing type hints (
def foo(x, y):with no annotations)
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.
- 3d ago First seen · 127 lines · 20 tokens per session scan A a3083572d488
cleanup is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,114 once invoked, about $0.0001 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
syllago-author
/home/hhewett/.local/src/syllago/content/agents/syllago-author/AGENT.md.
feature-flow
Build, test, verify, and review an already planned feature. Operates on a feature branch off trunk; prepares a PR but does not merge.
review
Review PR and build output for quality, security, and compliance. Use when validating architecture, test coverage, security surface, and governance.
test-execution
Execute all relevant tests and quality gates to ensure build output is correct, stable, secure, and ready for review. This is feature-flow's Phase 3 (and Phase 3.5 for live-system verification) — local, pre-push verification. Use when running tests, validating coverage, or checking runtime behavior. Distinct from the…
design
Convert the specification into a clear, actionable technical design with architecture, components, interfaces, and data flows. Use when translating requirements into a buildable system design.
learn
Product retrospective agent. Runs after a release, after a measure agent anomaly flag, or at end of sprint. Maps findings to DORA AI capabilities and produces plan agent action items. Distinct from fawkes learn.md which handles platform incident postmortems.