AutoDev is an AI-native, multi-agent development platform that supports workflows such as document research, coding, code review, data queries, artifact creation, and web interaction. It runs across environments including IntelliJ IDEA, VS Code, command-line tools, desktop and mobile applications, web runtimes, and servers. The catalogue skills extend its coding-agent workflows.
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 skills add phodal/auto-dev --skill refactorgit clone --depth 1 https://github.com/phodal/auto-devWrote 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/skills/phodal/auto-dev/refactor)<a href="https://agentmods.dev/skills/phodal/auto-dev/refactor"><img src="https://agentmods.dev/badge/skills/phodal/auto-dev/refactor/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/skills/phodal/auto-dev/refactor"><img src="https://agentmods.dev/badge/skills/phodal/auto-dev/refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.00151 |
| Opus 5.5 | $0.00004 | $0.00060 |
| Sonnet 5.5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
refactor 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.
What it actually says
Code Refactoring
You are an expert software engineer specializing in code refactoring.
Refactoring Request
$ARGUMENTS
Refactoring Focus
- Code Smells: Long methods, large classes, duplicate code
- Design: SOLID principles, design patterns
- Performance: Algorithm efficiency, resource management
- Maintainability: Readability, testability, modularity
Output Format
Before (Current Code)
Show current implementation with issues
After (Refactored Code)
Show improved implementation
Improvements Made
List all improvements with explanations
Project: $PROJECT_NAME
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 · 33 lines · 10 tokens per session scan A 1e1216ffbf2f
refactor is a skill published in the GitHub repository phodal/auto-dev (4,558 stars, last pushed 20d ago), licensed MPL-2.0. It adds 10 tokens to every session and 151 once invoked, about $0.0000 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 skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
deslop
Remove AI-generated code slop and clean up code style.
code-review
A structured code review process covering security, correctness, speed, and maintainability. Code review means checking source code for defects and risks before it is shipped.
review
Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from git status, or to review a specific backlog task by id such as task-65 or TASK-65. Also trigger when the user says things like "review", "review current changes", "check…
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.
review-async-lifecycle
Normative reviewer for EDT safety, coroutines, cancellation, read/write actions, disposal, listeners and async lifecycle in the explyt spring-plugin. Use during orchestrated code review when the diff touches threading, background tasks, read or write actions, listeners, MessageBus, Disposable ownership or progress…