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 skills/ccplugins/awesome-claude-code-plugins/claude-bionifynpx skills add ccplugins/awesome-claude-code-plugins --skill claude-bionifygit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/ccplugins/awesome-claude-code-plugins/claude-bionify)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/claude-bionify"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/claude-bionify.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.00084 | $0.01019 |
| Opus 5 | $0.00042 | $0.00509 |
| Sonnet 5 | $0.00017 | $0.00204 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
claude-bionify 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- claude-bionify — 89% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-bionify control
Background knowledge for answering questions about the claude-bionify plugin, which bolds the leading part of each word in Claude's responses (cosmetic bionic reading). Use it to recommend the right command and the exact key a user needs.
When to use
Load this skill when the user wants to:
- Change a setting (boldness, boundary, word length, acronyms, URLs, headings).
- Turn the formatting on, off, or toggle it.
- Check the current state or reset overrides.
- Learn what
/claude-bionifycommands exist.
Settings
Each setting has a default in plugin.json and a short key used by the live
/claude-bionify:set command. The set key is what you pass to the command, and it is
shorter than the plugin.json field name.
| Setting | set key |
Default | Values | Meaning |
|---|---|---|---|---|
| Fixation strength | fixation (alias strength) |
0.5 |
0.1 to 0.9 |
Fraction of each word bolded; higher is bolder. Applies to the fraction boundary only. |
| Bold boundary | boundary |
fraction |
fraction, syllable, log |
fraction uses the fixation strength; syllable bolds up to the first syllable; log grows logarithmically so long words are bolded less. |
| Minimum word length | minlen |
4 |
1 or greater |
Words shorter than this stay unbolded. |
| Skip acronyms | acronyms |
true |
on, off |
Leave ALL-CAPS acronyms such as API or JSON unbolded. |
| Protect URLs, paths, files | urls |
true |
on, off |
Do not bold inside URLs, emails, file paths, or filenames. |
| Skip headings | headings |
true |
on, off |
Leave markdown headings (lines starting with #) unbolded. |
Commands
All commands live under the /claude-bionify namespace.
| Command | Argument | Action |
|---|---|---|
/claude-bionify:status |
none | Show the current settings and whether bionify is on. |
/claude-bionify:on |
none | Enable bionic formatting. |
/claude-bionify:off |
none | Disable bionic formatting. |
/claude-bionify:toggle |
none | Flip bionify on or off. |
/claude-bionify:set |
<key> <value> |
Override one setting live. Keys: fixation (or strength), boundary, minlen, acronyms, urls, headings. |
/claude-bionify:reset |
none | Clear live overrides and restore the plugin.json defaults. |
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 · 67 lines · 84 tokens per session scan A e5b4560fc381
claude-bionify is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,019 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…