Borrowing it
Nothing to install: this file belongs to BloomBooks/BloomDesktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BloomBooks/BloomDesktop/master/.claude/skills/resume-ckeditor/SKILL.mdgit clone --depth 1 https://github.com/BloomBooks/BloomDesktopWrote 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/bloombooks/bloomdesktop/resume-ckeditor)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/resume-ckeditor"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/resume-ckeditor/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/bloombooks/bloomdesktop/resume-ckeditor"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/resume-ckeditor.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.00794 |
| Opus 5.5 | $0.00026 | $0.00318 |
| Sonnet 5.5 | $0.00013 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
resume-ckeditor 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume the CKEditor-retirement project (BL-6681)
This is a deliberately long-running project spanning many sessions and many rebases against a
moving master. Its state lives in docs/retire-ckeditor/, not in any session's memory.
Do this, in order
-
Read the state.
docs/retire-ckeditor/PROGRESS.md— the live log, current phase, and next actions. Start here.docs/retire-ckeditor/PLAN.md— the staged plan (Stages 0–6). Authoritative for what to do. §10 holds the settled decisions and what the first review changed — do not re-litigate anything settled there; if you think a settled point is wrong, say so explicitly to the user rather than quietly changing course. §11 records what BL-6681 itself asks for, and what on it is already obsolete.docs/retire-ckeditor/BEHAVIOR-INVENTORY.mdif it exists — the behaviours that must survive.
-
Orient in git.
git status,git log --oneline -15, and note the current branch. Because the plan deliberately avoids long-lived branches, you may well be onmasterwith nothing in flight; that is the normal resting state between stages, not a sign something was lost. -
Check for drift. Other work lands on
mastercontinuously. Before continuing a stage, confirm the files it touches still look the way the plan assumes — the plan cites specificfile:linelocations, and those move. If a citation has gone stale, fix the plan text as part of the work; a plan nobody trusts is worse than no plan. -
Continue from the next unchecked item in PROGRESS.md's "Next actions". Confirm with the user which stage to work on if more than one is plausible.
-
Before ending the session (or when you sense you are running low on context), update
PROGRESS.md: what you did, what you learned, the branch/PR, and a revised "Next actions". Do this even if the work is half-finished — especially then.
Ground rules for this project
- New code goes in new files (
bookEdit/undo/,bookEdit/textEditor/). Edits to existing files should be one-line dispatches wherever possible, and as late in the plan as possible. This is the project's whole defence against rebase pain. - Don't keep a long-lived branch. Each stage is designed to be its own small, green,
flag-inert PR onto
master. - Deletion commits (Stage 5) are regenerated, never rebased. If one conflicts, throw it away and redo it mechanically.
- Build and test through the wrappers, never bare
dotnet/vite—build/agent-dotnet.shandbuild/agent-vite.sh— because the developer usually has a Bloom running via./go.sh. SeeAGENTS.md. Never run the fullpnpm build. - To see a change in the running Bloom, just edit the source (the Vite dev server pushes it in)
and observe via the
run-bloomskill. No build.
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 · 52 lines · 65 tokens per session scan A d52514aad7f8
resume-ckeditor is a skill published in the GitHub repository BloomBooks/BloomDesktop (43 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 794 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-09-22.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.