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 rhein1/fable5-codex --skill fable-sweepgit clone --depth 1 https://github.com/rhein1/fable5-codexWrote 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/rhein1/fable5-codex/fable-sweep)<a href="https://agentmods.dev/skills/rhein1/fable5-codex/fable-sweep"><img src="https://agentmods.dev/badge/skills/rhein1/fable5-codex/fable-sweep/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/rhein1/fable5-codex/fable-sweep"><img src="https://agentmods.dev/badge/skills/rhein1/fable5-codex/fable-sweep.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.00065 | $0.00872 |
| Opus 5.5 | $0.00026 | $0.00349 |
| Sonnet 5.5 | $0.00013 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
fable-sweep 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fable Sweep
Perform broad changes with discovery first and scoped edits second. Do not mutate unrelated worktree changes.
For ECF-style governed runs, use ../../references/ecf-run-contract.md. For large sweeps, use real Codex subagents when the runtime exposes a subagent tool and the user has not opted out; treat repo-wide renames, migrations, consistency passes, generated-surface syncs, docs/tests syncs, and "find every place" tasks as large by default. Otherwise run single-agent multi-lens and say why no subagents were used when workflow trace is requested.
Use the centralized capability-aware profiles in ../../references/model-support.md and ../../config/model-profiles.json. Keep model and reasoning selections configurable, preserve explicit overrides, and record the requested and actual coordinator model and effort and requested and actual worker model plus any fallback. Request parallel delegation only for useful disjoint lenses; report single-agent multi-lens when no workers ran. The coordinator owns synthesis and final verification. Never claim a model, effort or subagent ran without runtime evidence.
Workflow
- Restate the target change and authority boundaries.
- Declare the ECF run mode when the user asks for ECF, subagents, or a receipt. Use
multi-agentonly when real subagents will be spawned. - Read repo instructions and identify generated, public, config, docs, tests, and serialized surfaces that may need updates.
- Build a complete hit list using fast search first:
rgfor identifiers, strings, docs, config, tests, migrations, snapshots, and generated files- language-aware search or AST tools when available and useful
- import/caller lookup for behavior changes
- Classify hits:
- must edit
- must preserve for compatibility
- generated or external
- uncertain
- Make scoped edits only after the discovery map is clear. Preserve existing style and local helper APIs.
- Run targeted validation. Include tests, lint, type checks, snapshot regeneration, or schema validation when relevant.
- Report changed files, preserved compatibility points, validation, and remaining uncertain areas.
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.
- 9d ago Changed 024e8030c96b
- 1mo ago Changed · +15 lines 370e73087379
- 2mo ago First seen · 43 lines · 65 tokens per session scan A 6a14e1080642
fable-sweep is a skill published in the GitHub repository rhein1/fable5-codex (4 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 872 once invoked, about $0.0003 per session on Opus 5.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
robin
Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
gerrit-workflow
This skill should be used when the user asks to "submit a change to Gerrit", "push for review", "upload a patch", "update a change in Gerrit", "add a patch set", "work with Gerrit", "push to refs/for", "fix a missing Change-Id", "amend a Gerrit change", or any task involving git operations in a repository hosted on…
gerrit-task-query
Use when asked to check, list, or act on tasks for a Gerrit change. Triggers on phrases like "what tasks are blocking", "which tasks are actionable", "check task status", "what do I need to do for this change", "what is blocking this change".
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.