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 sd0xdev/sd0x-harness --skill de-ai-flavorgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/de-ai-flavor)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/de-ai-flavor"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/de-ai-flavor/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/sd0xdev/sd0x-harness/de-ai-flavor"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/de-ai-flavor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00055 | $0.00588 |
| Opus 5 | $0.00028 | $0.00294 |
| Sonnet 5 | $0.00011 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
de-ai-flavor 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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
De-AI-Flavor Skill
Trigger
- Keywords: de-ai, remove AI traces, humanize document, de-ai-flavor, humanize
When NOT to Use
- Co-Authored-By in CHANGELOG (Git convention)
- Documents discussing AI technology (topic itself requires it)
- Quoting others' AI-related content
- Variable/function names in code
Usage
/de-ai-flavor docs/xxx.md # Process specified file
/de-ai-flavor docs/ # Process all .md in directory
/de-ai-flavor # Process .md in git diff
Detection Rules
| Type | Pattern | Action |
|---|---|---|
| Tool names | Claude/Codex/GPT/AI assistant | Remove |
| Boilerplate | "Let me...", "First...then...", "In conclusion" | Rewrite |
| Over-structuring | One sentence per heading, too many #### levels | Simplify |
| Service tone | "Hope this helps", "If you have questions..." | Remove |
| Self-description | "Next I will...", "I will proceed to..." | Remove |
| Iteration leaks | "Round 1/Round 2/Round N" | Rewrite |
Workflow
Scan file -> Mark AI traces -> Remove/Rewrite/Simplify -> Output summary
Verification
- All tool names removed
- Boilerplate rewritten to natural tone
- Structure not overly flat or nested
Output Format
## De-AI-Flavor Results
**File**: `docs/xxx.md`
| Line | Original | Change | Reason |
| ---- | --------------------- | ----------------------- | ---------------- |
| 15 | Let me explain... | Removed | AI self-description |
| 32 | Claude suggests... | Changed to "Suggest..." | Tool name |
**Stats**: Removed 3 tool names | Rewrote 5 boilerplate | Simplified 2 structures
Examples
Input: /de-ai-flavor docs/tech-spec.md
Action: Scan -> Remove "Claude suggests" -> Rewrite "Let me explain" -> Output summary
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.
- 11d ago First seen · 77 lines · 55 tokens per session scan A ec6f1d44a119
de-ai-flavor is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 588 once invoked, about $0.0003 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
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.
architecture
Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability. For multi-component, API, schema, auth, or integration-heavy work. For retrofitting existing code, use codebase-hygiene instead.