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 uqeu/estelle-cli --skill refactor-rfcgit clone --depth 1 https://github.com/uqeu/estelle-cliWrote 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/uqeu/estelle-cli/refactor-rfc)<a href="https://agentmods.dev/skills/uqeu/estelle-cli/refactor-rfc"><img src="https://agentmods.dev/badge/skills/uqeu/estelle-cli/refactor-rfc/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/uqeu/estelle-cli/refactor-rfc"><img src="https://agentmods.dev/badge/skills/uqeu/estelle-cli/refactor-rfc.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.00000 | $0.00297 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
refactor-rfc 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
refactor-rfc
Estelle's debt-paydown planner. Big-bang rewrites are how refactors die; this files a plan of tiny, individually-safe commits that keep the build green the whole way.
Procedure
- Name the smell — the concrete pain (duplication, tangled module, untestable seam) and the cost of leaving it.
- Draw the target shape — what the code looks like after, grounded against the current repo structure so the endpoint is real.
- Sequence tiny commits — an ordered list where each step is small, reversible, and green on its own; no step leaves the tree broken.
- Guard with tests first — ensure characterization tests cover current behavior before moving code, so refactors stay behavior-preserving.
- Order for safety — front-load the low-risk mechanical steps; isolate the one genuinely risky change and flag it.
- File the RFC — publish to the tracker as an RFC; execute each commit through
verify-gate.
Output
An RFC with the smell, the target shape, and an ordered checklist of small safe commits. Serves debt paydown incrementally, without big-bang risk.
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 · 20 lines · 0 tokens per session scan A 310b43c49378
refactor-rfc is a skill published in the GitHub repository uqeu/estelle-cli (0 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 297 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-12.
Other skills, from other repositories
cocosearch-commit
Use when committing changes — analyzes staged (or unstaged) diffs with CocoSearch semantic search and dependency impact to generate comprehensive Conventional Commit messages. Reviews changes thoroughly, then asks user to approve, edit, or abort the commit.
loop-gh-pr
A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.
git-iris
Use this skill when generating commit messages, pull request descriptions, release notes, changelogs, or code reviews in a repository where git-iris is available. Activates on requests like "commit this", "write a commit message", "draft a PR", "generate release notes", "write a changelog", or "review my changes" when…
requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
fix
Read this repo's open issues, triage them, and open one pull request per issue that can be fixed without a judgement call. Issues that need a decision, or that look stale or superseded, are reported with a recommendation rather than guessed at.
git
This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", or performs any git/GitHub operation.