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 skills add samber/cc-skills --skill humaniseur-frgit clone --depth 1 https://github.com/samber/cc-skillsWrote 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/samber/cc-skills/humaniseur-fr)<a href="https://agentmods.dev/skills/samber/cc-skills/humaniseur-fr"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/humaniseur-fr/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/samber/cc-skills/humaniseur-fr"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/humaniseur-fr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00167 | $0.10782 |
| Opus 5 | $0.00084 | $0.05391 |
| Sonnet 5 | $0.00033 | $0.02156 |
| Haiku 4.5 | $0.00017 | $0.01078 |
Grade A, and why
humaniseur-fr 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 6d 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 — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Humaniseur : supprimer les patterns d'écriture IA du français
Your task
When given French text to humanize:
- Clarify the target register first - Abbreviations, argot, orality, emojis and typography all depend on the expected niveau de langage. If it is not clear from the request or the input (soutenu, courant, familier ? for which medium ?), ask the user before starting to humanize
- Identify AI patterns - Scan for all 38 patterns listed below
- Rewrite problematic sections - Replace AI-isms with natural French alternatives
- Preserve meaning - Keep the core message intact
- Maintain voice - Match the intended tone and register
- Add soul - Don't just remove bad patterns; inject actual personality (see Part 4)
- Do a final anti-AI pass - Ask: "Qu'est-ce qui rend ce texte évidemment généré par IA ?" Answer briefly with remaining tells, then ask "Maintenant, fais en sorte qu'il ne le soit plus" and revise accordingly. Apply the three-signal rule: one isolated marker is noise (most are normal French), but three or more co-occurring in the same passage make a reader flinch — revise until no paragraph accumulates three
The 80 % rule: imperfect compliance is the point
Follow the humanizer rules most of the time — not always. It is fine to leave roughly 20 % of this skill's instructions unapplied.
- Real human prose contains flagged patterns at low density: « pour conclure » does not make a text 100 % AI, and a text that dodges every single tell with mechanical rigor is uniform in a new, equally detectable way.
- Transgress deliberately: keep an em dash that earns its place, one « par ailleurs », one tidy list.
- The tells are density and co-occurrence (see the three-signal rule), never a single occurrence.
One pass only. Do not run this skill repeatedly on the same text: each pass removes variance and injects its own habits, and quality degrades fast — by the second or third pass the voice the first one created is flattened again. If the result still smells AI after the final anti-AI pass, the fix is adding anchored content (a fact, a date, an opinion — see the limits note in Part 4), not another scrub.
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.
- 6d ago Changed · +16 lines · -54 tokens per session 80ffd1cdca7b
- 11d ago First seen · 608 lines · 221 tokens per session scan A 6f720b328cdb
humaniseur-fr is a skill published in the GitHub repository samber/cc-skills (209 stars, last pushed 4d ago), licensed MIT. It adds 167 tokens to every session and 10,782 once invoked, about $0.0008 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-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
golang-dependency-injection
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture…
golang-design-patterns
Idiomatic Golang design patterns — functional options, constructor APIs, init() and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing…
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…