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 amadeus-dlc/amadeus --skill refactoring-packagesgit clone --depth 1 https://github.com/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/refactoring-packages)<a href="https://agentmods.dev/skills/amadeus-dlc/amadeus/refactoring-packages"><img src="https://agentmods.dev/badge/skills/amadeus-dlc/amadeus/refactoring-packages.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.1 | $0.00063 | $0.00265 |
| Opus 5 | $0.00032 | $0.00133 |
| Sonnet 5 | $0.00013 | $0.00053 |
| Haiku 4.5 | $0.00006 | $0.00026 |
Grade A, and why
refactoring-packages 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 7d 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
Refactoring Packages
Refactor structure in small, verifiable moves. Preserve behavior while improving dependency shape.
Workflow
-
Inventory the current package tree and dependency graph.
-
Identify cycles, large modules, unstable public APIs, and misplaced responsibilities.
-
Propose a target structure based on change reasons and dependency direction.
-
Move one coherent slice at a time.
-
Update imports, tests, build files, and public documentation as needed.
-
Run the relevant checks after each meaningful batch.
Reference
Read references/analysis-patterns.md for common structural smells and remedies.
Detailed Reference
For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.
Output
Return findings, target structure, migration checklist, executed changes, and verification results.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 36 lines · 63 tokens per session scan A c5ac04d6743f
refactoring-packages is a skill published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 16d ago), licensed Apache-2.0. It adds 63 tokens to every session and 265 once invoked, about $0.0003 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 skills, from other repositories
anti-monolith-guard
Prevent mixed-responsibility modules and uncontrolled file growth.
code-hygiene-refactor
Select a bounded, behavior-preserving code-hygiene batch.
agent-aegis
Security and privacy review for scoped changes.
PlanGate 計画整合性チェック
A checker that compares project planning documents with one another. It checks whether the product requirements, implementation plan, task list, and test cases describe the same work.
Architecture Traceability & Consistency
Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.