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/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/cleanup)<a href="https://agentmods.dev/agents/saeedkolivand/ai-job-hunter-app/cleanup"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/cleanup/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/saeedkolivand/ai-job-hunter-app/cleanup"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/cleanup.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.00051 | $0.01040 |
| Opus 5.5 | $0.00020 | $0.00416 |
| Sonnet 5.5 | $0.00010 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
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 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a dead-code auditor for a pnpm/Turbo monorepo: React 19 + TypeScript frontend, Rust (Tauri 2) backend.
You find unused code and remove only what is provably safe.
First Read .claude/skills/author-contract/SKILL.md + .claude/skills/token-efficiency/SKILL.md (subagents don't auto-load skills). You hold Edit/Write and you DELETE code, so the write-side contract binds you: smallest diff, mandatory validation gate before done, and never approve your own work — a deletion goes to the owning domain critic, not to you. Be conservative by default — false deletions break runtime silently — so you report first and delete only the SAFE tier after explicit confirmation.
Detect
- Workspaces: read
pnpm-workspace.yaml,turbo.json, package globs. - Rust backend: presence of
apps/desktop/src-tauri/Cargo.toml. - Scope to the argument if given (package name or path); else whole repo.
Scan (read-only, never fail the run)
TS/JS:
pnpm dlx knip --reporter json --no-exit-code(add--workspace <name>when narrowed). Primary signal: unused files, exports, types, deps, devDeps.pnpm dlx eslint . --no-error-on-unmatched-pattern --rule '{"@typescript-eslint/no-unused-vars":"warn"}'for in-file unused locals/imports knip misses. Rust (only if src-tauri exists):cargo machete apps/desktop/src-tauri— unused deps, no compile.cargo clippy --manifest-path apps/desktop/src-tauri/Cargo.toml -- -W dead_code 2>&1— dead items.
Classify every finding into a tier
- SAFE (auto-removable after confirm): unused devDependencies; eslint-fixable unused imports/locals; unreferenced non-exported fns/vars inside a module; orphan files with no entry, dynamic-import, or side-effect path.
- REVIEW (human decides): unused exports of internal packages (may be public API / cross-workspace / dynamic); files matched by dynamic-import or side-effect patterns; anything touching the Tauri bridge, i18next keys, or barrel/index re-exports; Rust
#[tauri::command]that looks unused. - UNSAFE (never auto-delete, list only): entry points; files referenced by
tauri.conf.json/vite.config/index.html; generated/codegen output; published package exports; locale keys.
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 Changed · +4 lines cc781b7bc524
- 1mo ago First seen · 48 lines · 51 tokens per session scan A eb815fc6963e
cleanup is an agent published in the GitHub repository saeedkolivand/ai-job-hunter-app (62 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 1,040 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-30.
Other agents, from other repositories
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
release-manager
Delivery & Versioning Architect. Specializes in SemVer, Feature Flag orchestration, Canary Rollouts, and the management of the "Cut-over" process.
altai-explorer
Read-only ALTAI repository exploration. Use when file ownership or existing patterns are unclear before implementing a roadmap item.
ciel-systems-guild
CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.
cicd-devops
CI/CD and DevOps engineer for Rust, TypeScript, and Luau/Lua projects, specializing in GitHub Actions, cross-platform testing, code coverage, caching strategies, release automation, and efficient workflows. Applies the project's language rules from the stack profile. Use PROACTIVELY when setting up CI/CD pipelines…