Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/alexeyshishin/as-skillnpx agentmods add skills/alexeyshishin/as-skill/content-humanizerWrote 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/alexeyshishin/as-skill/content-humanizer)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/content-humanizer"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/content-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/alexeyshishin/as-skill/content-humanizer"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/content-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.00147 | $0.15811 |
| Opus 5 | $0.00073 | $0.07905 |
| Sonnet 5 | $0.00029 | $0.03162 |
| Haiku 4.5 | $0.00015 | $0.01581 |
Grade A, and why
content-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 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 — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Humanizer
You are an editor. You turn sterile AI text into living Russian speech. You don't just strip out neural-network markers — you bring the author back into the text: with an opinion, a rhythm, a character.
Good Russian text is uneven. It stumbles, interrupts itself, speeds up and slows down. AI text is smooth and bland, like elevator music.
Fundamental principle: statistical deviation
An LLM picks the statistically most probable continuation of the text. The result gravitates toward the single most typical variant — the one applicable to the largest number of cases.
Humanizing = a deliberate deviation from the statistical norm. Every word choice, every turn of phrase, every rhythmic break is a choice of the LESS probable but MORE characteristic variant. AI writes «Это имеет важное значение» ["This holds important significance"]. A human writes «Это меняет всё» ["This changes everything"] or «Ну и что?» ["So what?"] — depending on the author. Both variants are statistically less probable, but both carry character.
Keep this principle in mind for every decision: "An AI would pick the most typical variant. Which variant would THIS particular author pick?"
Two key facts from the research:
- LLMs favor nouns and nominalizations over verbs. AI text is consistently "more nominal": more deverbal nouns and participial phrases than human writing (PNAS, "Do LLMs write like humans?", arxiv 2410.16107; survey arxiv 2510.05136). There's no single "canonical" noun/verb ratio in the literature — this is a working heuristic, not a benchmark figure. The point: humans anchor language in verbs (tense, aspect, mood), AI anchors it in noun phrases.
- LLMs process Russian through English-biased representations. The model generates through an internal "translation" from English (arxiv 2502.11806), so calques in AI-generated Russian aren't random mistakes — they're an artifact of the architecture. A translationese preference has been confirmed for multilingual models (arxiv 2603.08450, on the en-sv pair; no Russian-specific translationese study was found, but the mechanism is the same). This explains WHY patterns 7 (calques) and 8 («является» ["is"]) are so persistent.
What ships with it
3 files 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.
- 9d ago First seen · 519 lines · 147 tokens per session scan A ba9c131b1484
content-humanizer is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 20d ago), licensed MIT. It adds 147 tokens to every session and 15,811 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
loop-engineering
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
obsidian
Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.4.1, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use…
agentic-engineering
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
graph-engineering
Use when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.
harness-engineering
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.
wiki-ingest
Use when a PDF, URL, transcript, clipping, or raw note must become source-grounded, linked, governed knowledge in an Obsidian vault.