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 imMamdouhaboammar/get-things-done --skill refactor-safelygit clone --depth 1 https://github.com/imMamdouhaboammar/get-things-doneWrote 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/immamdouhaboammar/get-things-done/refactor-safely)<a href="https://agentmods.dev/skills/immamdouhaboammar/get-things-done/refactor-safely"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-things-done/refactor-safely/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/immamdouhaboammar/get-things-done/refactor-safely"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-things-done/refactor-safely.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.00015 | $0.00303 |
| Opus 5.5 | $0.00006 | $0.00121 |
| Sonnet 5.5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
refactor-safely 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.
This is a copy
100% identical to refactor-safely — 27 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.
What it actually says
Refactor Safely
Use the knowledge graph to plan and execute refactoring with confidence.
Steps
- Use
refactor_toolwith mode="suggest" for community-driven refactoring suggestions. - Use
refactor_toolwith mode="dead_code" to find unreferenced code. - For renames, use
refactor_toolwith mode="rename" to preview all affected locations. - Use
apply_refactor_toolwith the refactor_id to apply renames. - After changes, run
detect_changes_toolto verify the refactoring impact.
Safety Checks
- Always preview before applying (rename mode gives you an edit list).
- Check
get_impact_radius_toolbefore major refactors. - Use
get_affected_flows_toolto ensure no critical paths are broken. - Run
find_large_functions_toolto identify decomposition targets.
Token Efficiency Rules
- Start with
get_minimal_context_tool(task="<your task>")before other graph tools. - Use
detail_level="minimal"on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
- Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
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 · 30 lines · 15 tokens per session scan A 95e60c797d62
refactor-safely is a skill published in the GitHub repository imMamdouhaboammar/get-things-done (2 stars, last pushed 24d ago), licensed MIT. It adds 15 tokens to every session and 303 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to refactor-safely, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
ship-it-or-fix-it
Oracle-frozen Builder and independent-Judge convergence cycle. Load ONLY when the operator explicitly sets Governance Dial G2 for the task, or explicitly names this skill or an active work unit already running it. Never auto-activate on task class, such as security, auth, or payments. If a task seems to warrant G2 and…
test-verification
Requires behavioral, failure-path, and durable-seam evidence for tests and review. Use when writing tests, reviewing test coverage, assessing behavioral test quality, or accepting high-risk behavior on test evidence.
luna
Reviews code for objective correctness, security, and reliability.
max
Cleans up and improves existing code without changing behavior.
auto-research
Research uncertain questions with an explicit, user-approved web search or ChatGPT consultation, then present options and wait for implementation approval.
architect-review
Master software architect specializing in modern architecture.