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 agentmods add commands/samibs/skillfoundry/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/commands/samibs/skillfoundry/refactoring-strategist)<a href="https://agentmods.dev/commands/samibs/skillfoundry/refactoring-strategist"><img src="https://agentmods.dev/badge/commands/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 | $0.00000 | $0.00404 |
| Opus 5 | $0.00000 | $0.00202 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 yesterday.
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.
- yesterday First seen · 65 lines · 0 tokens per session scan A 1ef80e3513db
refactoring-strategist is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 404 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.