Borrowing it
Nothing to install: this file belongs to flowing-abyss/obsidian-hybrid-search. 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/flowing-abyss/obsidian-hybrid-search/master/.ai/skills/humanizer/SKILL.mdgit clone --depth 1 https://github.com/flowing-abyss/obsidian-hybrid-searchWrote 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/flowing-abyss/obsidian-hybrid-search/humanizer)<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/humanizer"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/humanizer/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/flowing-abyss/obsidian-hybrid-search/humanizer"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/humanizer.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.00057 | $0.00475 |
| Opus 5.5 | $0.00023 | $0.00190 |
| Sonnet 5.5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
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 today.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Humanizer for technical writing
Read references/patterns.md before editing prose.
Workflow
Identify the audience and the concrete change, write a draft, check it for AI patterns and factual drift, then rewrite awkward paragraphs around their main point. Match a supplied writing sample and the repository's language. Use plain technical prose when no sample is supplied. Do not invent personal anecdotes, user praise, benchmark numbers, or verification results.
Preserve names, versions, dates, compatibility commitments, opt-in/offline behavior, migration and rollback instructions, warnings, and citations. Keep code blocks, inline code, commands, file paths, package metadata, link targets, YAML metadata, and required template headings unchanged. A smoother sentence must not make an unverified claim sound verified or erase a limit.
Embedded Use
For another task's PR, release, or README work, return only the final prose; keep the draft and self-check internal. Do not put AI-detection commentary or intermediate variants into the artifact. For a standalone pasted-text request, follow the reference's default output unless the user specifies otherwise. File work writes only the final prose to the requested file.
- Pull requests: state the concrete problem and resulting behavior, then verified checks and material limitations. Keep code review findings intact.
- Releases: explain what users can now do, what changed, compatibility and migration requirements. Review an auto-generated changelog before publishing; the existence of a draft release does not prove its notes are accurate.
- README: preserve working installation instructions, examples, links, and badges. Edit it only when the task authorizes README changes; invoking this skill through a release or PR never authorizes unrelated documentation edits.
The skill edits wording only. Posting a PR, editing a GitHub release, or publishing remains governed by the parent task's authorization. It does not authorize any network call inside the utility.
What ships with it
1 file beside SKILL.md 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.
- today First seen · 44 lines · 57 tokens per session scan A 0eecb1d791be
humanizer is a skill published in the GitHub repository flowing-abyss/obsidian-hybrid-search (113 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 475 once invoked, about $0.0002 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-10-24.
Other skills, from other repositories
codemark
Manage structural code bookmarks that survive refactoring. Use when the user says "remember this", "bookmark this", "save this location", "load my bookmarks", "what do I have bookmarked", "mark this code", "codemark", or when starting a new session and needing to reload context from a previous session. Also use…
qdrant-vector-search
High-performance vector similarity search engine for RAG and semantic search. Use when building production RAG systems requiring fast nearest neighbor search, hybrid search with filtering, or scalable vector storage with Rust-powered performance.
notebrain-assistant
Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like…
palaia-memory
Check this person's shared memory before answering anything about their own work, and add to it when something is worth keeping. It holds their projects, decisions and reasons, house conventions (naming, commit messages, tests, releases, review and escalation), people and hard-won details, and every AI tool they use…
palaia-messenger
Register this session with the shared directory so other AI sessions and this person's dashboard can see what you are doing, then use it to reach another live session directly instead of relaying everything through the person. Use it at the start of a task, before picking one up, when your work depends on or informs…
palaia-capture
Save what this person tells you into their shared memory, which every AI tool they use can read. Use it the moment they state a decision and the reason for it, a convention, a correction, or a detail that was expensive to work out — including when they mention it in passing on the way to a different question. Save it…