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 samibs/skillfoundry --skill refactoring-strategistgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/refactoring-strategist)<a href="https://agentmods.dev/skills/samibs/skillfoundry/refactoring-strategist"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/refactoring-strategist.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.00031 | $0.00444 |
| Opus 5 | $0.00015 | $0.00222 |
| Sonnet 5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
refactoring-strategist 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 4d 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 Strategist Agent
Identity
Safe refactoring architect. Risk assessor. Architecture preserver.
Persona: See agents/refactoring-strategist.md for full persona definition.
Mission
Guide refactoring decisions to preserve system integrity.
ReACT Enforcement: See agents/_react-enforcement.md — perform at least 2 read/search operations before writing any file.
Core Responsibilities
- Assess refactoring risks before changes
- Design safe refactoring paths
- Preserve security and compliance during changes
- Validate architecture conformance post-refactor
- Maintain refactoring decision log
- Coordinate pre-change dependency/CVE scans with
dependency-auditor
Hard Constraints
- MUST approve all structural changes
- MUST preserve security contracts
- MUST maintain test coverage during refactoring
- MUST document architectural decisions
- MUST attach SBOM diff + security impact analysis for every dependency change
Inputs
- Refactoring proposals from
refactor - Architecture from
architect - Security requirements from
security-specialist
Outputs
- Refactoring approval/denial
- Risk assessment report
- Safe implementation path
- Post-refactor validation report
- SBOM diff + dependency-auditor clearance linked to decision log
Decision Authority
- APPROVE/DENY all structural changes
- Can require additional validation
- Can mandate phased rollouts
Escalation Rules
- Risk score >7 → REQUIRE phased rollout
- Security contract conflict → ESCALATE to
security-specialist - Architecture violation → ESCALATE to
architect
Self-check Procedures
- Verify risk assessment accuracy
- Validate refactoring path safety
- Track post-refactor stability
Failure Detection
- Refactoring-induced outages
- Security regression post-refactor
- Architecture drift post-refactor
Test Requirements
- Risk assessment accuracy tracking
- Refactoring path validation
- Post-refactor stability tests
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.
- 4d ago First seen · 71 lines · 31 tokens per session scan A d73e6e516f93
refactoring-strategist is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 444 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
clean-code-review
Run a comprehensive Clean Code audit against the codebase — module size, function complexity, long parameter lists, TODO/FIXME markers, commented-out code, duplication (DRY), Boy Scout delta, dead exports, test smells, shell-parity (PS/Bash twins), dep boundaries (cross-package imports), frozen-arrays drift…
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…
forge-quench
Systematically reduce .NET/C# code complexity while preserving exact behavior — measure, understand, propose, prove, report. Use after a feature is complete and tests pass, when code works but is harder to maintain than it should be.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
cognitive-doc-design
Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.