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.
git clone --depth 1 https://github.com/mrDesign-ww/vault-osWrote 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/plugins/mrdesign-ww/vault-os/humanizer)<a href="https://agentmods.dev/plugins/mrdesign-ww/vault-os/humanizer"><img src="https://agentmods.dev/badge/plugins/mrdesign-ww/vault-os/humanizer.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
humanizer 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 2d 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.
This is a copy
100% identical to humanizer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "humanizer",
"description": "Remove signs of AI-generated writing from text, making it sound more natural and human. Based on Wikipedia's \"Signs of AI writing\" guide.",
"version": "2.9.1",
"author": {
"name": "blader",
"url": "https://github.com/blader"
},
"homepage": "https://github.com/blader/humanizer",
"repository": "https://github.com/blader/humanizer",
"license": "MIT",
"keywords": ["writing", "editing", "ai-detection", "humanize", "prose", "style"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 93 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 15 lines scan A f31bf57f37ea
humanizer is a plugin published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to humanizer, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
coaltipple
CoalTipple — model/effort router for Claude Code. Delegates a task you CAN do but is large+cheap DOWN to a lower tier to save tokens; escalates a task beyond the current tier UP for quality — up to Fable 5, the top rung (a consent-gated, real-money spawn). Two-knob routing (tier × effort, effort-before-tier), an alias.
pict-test-designer
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected…
write-a-readme
Turn codebases into accurate, on-brand READMEs with editable SVG banners.
swift-performance-pro
Performance: Instruments, SwiftUI render cost, memory and retain cycles, launch time, lists.