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 DavidROliverBA/ArchitectKB --skill de-ai-ifygit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/de-ai-ify)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/de-ai-ify"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/de-ai-ify/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/davidroliverba/architectkb/de-ai-ify"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/de-ai-ify.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.00015 | $0.00573 |
| Opus 5 | $0.00008 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
de-ai-ify 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/de-ai-ify
Strip AI-sounding patterns from generated text and rewrite to be natural, direct, and human.
Usage
/de-ai-ify <note path> # Rewrite a specific note
/de-ai-ify --section <heading> # Rewrite only a specific section
/de-ai-ify --clipboard # Rewrite text from clipboard context
Instructions
-
Read the target note or receive the text to rewrite
-
Identify AI patterns — flag any of the following:
Filler phrases to remove:
- "Let's dive into...", "Let's explore..."
- "I'd be happy to..."
- "It's worth noting that..."
- "It's important to understand..."
- "In today's rapidly evolving..."
- "This is a great question"
- "As we can see..."
- "Moving forward..."
Hedging to reduce:
- "It could potentially..." → state directly or remove
- "This might suggest..." → "This suggests..." or cut
- "It's possible that..." → state the thing or qualify once
- Stacking qualifiers: "perhaps", "maybe", "somewhat", "arguably"
Structural patterns to fix:
- Excessive bullet points where prose would be clearer
- Every paragraph opening with a transition word
- Formulaic "In conclusion..." / "To summarise..." wrap-ups
- Numbered lists for things that aren't sequential
- Restating the question before answering it
Tone patterns to adjust:
- Overly enthusiastic ("fantastic", "incredible", "amazing")
- Corporate-bland ("leverage", "synergise", "drive value")
- Sycophantic agreement before every response
-
Rewrite the flagged sections:
- Keep the author's intent and meaning
- Use active voice, concrete language
- Prefer shorter sentences
- Let the content speak — cut throat-clearing
- Preserve any technical accuracy and wiki-links
- Maintain frontmatter unchanged
-
Show the diff — present before/after for each changed section so the user can review
-
Apply changes only after user confirms
Guidelines
- Do NOT change frontmatter, wiki-links, or Dataview queries
- Do NOT remove content — only rephrase
- Do NOT add new content or expand the text
- Preserve the author's voice where it comes through
- When in doubt, cut rather than rephrase
- UK English throughout
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 · 74 lines · 15 tokens per session scan A e656dc6aa20c
de-ai-ify is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 573 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…