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 Fergius-Engineering/instincts --skill de-ai-prosegit clone --depth 1 https://github.com/Fergius-Engineering/instinctsWrote 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/fergius-engineering/instincts/de-ai-prose)<a href="https://agentmods.dev/skills/fergius-engineering/instincts/de-ai-prose"><img src="https://agentmods.dev/badge/skills/fergius-engineering/instincts/de-ai-prose.svg" alt="Measured on agentmods" 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.00030 | $0.00674 |
| Opus 5 | $0.00015 | $0.00337 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
de-ai-prose 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The rule
Readers can tell when a machine wrote the text, and it costs trust the same way sloppy code does. After you write any prose a person will read, read it back once and cut the tells. Plain words, varied sentences, say the thing instead of announcing you're about to say it.
Fires when
About to show a human a README, a doc page, a commit or PR body, a changelog entry, a UI string, store copy — anything a person will read as writing rather than run as code.
Tells to cut
- Signposting sentences: "Here's the thing.", "That's the point.", "This is the important part.", "By the end you'll know what, why, and how."
- Closers like "That's it." or "And that's all there is to it."
- Em-dash overuse as the default connector. The constant em-dash rhythm is a fingerprint.
- Parallel triads everywhere ("a texture, a config, a script"), over-balanced sentences, the list-of-three cadence.
- Arrow constructions in prose ("write one function -> the whole thing appears").
- A table for everything; bold sprinkled on every other phrase as decoration.
- Bullet lists where every item opens with a bold label ("Fast: ...", "Simple: ..."), parallel from top to bottom.
- Cutesy section names and peppy filler ("the payoff", "the ones that bite").
- Paragraphs that are all the same length and shape. Too tidy.
How to apply
Plain, varied sentences. Some short. Let one run long and a little uneven, like a person typing.
Say it directly instead of signposting it. Use em-dashes rarely. Prefer periods, commas, "and". Vary connectors. Cutting an em-dash means rebuilding the sentence (a comma, a colon, parentheses, or two sentences), not swapping a different mark into the same joint.
Keep bold for genuinely key terms, not decoration. Drop a table where a sentence reads more naturally.
Read it back and ask: "would a tired engineer writing this actually phrase it this way?" If it sounds like a polished AI explainer, flatten it.
Before / after
Before (AI voice):
Here's the thing about our caching layer — it's fast, it's simple, and it's reliable. The payoff? Sub-millisecond reads.
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 First seen · 57 lines · 30 tokens per session scan A 81596b1782f5
de-ai-prose is a skill published in the GitHub repository Fergius-Engineering/instincts (2 stars, last pushed 12d ago), licensed MIT. It adds 30 tokens to every session and 674 once invoked, about $0.0002 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
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…
memstack-product-feedback-analyzer
Use this skill when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and prioritize into actionable reports. Do NOT use for competitor analysis or market research.
memstack-seo-meta-tag-optimizer
Use this skill when the user says 'meta tags', 'title tag', 'meta description', 'optimize meta', 'SERP preview', or needs to write or optimize HTML meta tags for better search visibility and click-through rates. Do NOT use for schema markup or full site audits.