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 OutThisLife/brooklyn-skills --skill no-tropesgit clone --depth 1 https://github.com/OutThisLife/brooklyn-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/outthislife/brooklyn-skills/no-tropes)<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/no-tropes"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/no-tropes/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/outthislife/brooklyn-skills/no-tropes"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/no-tropes.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.00064 | $0.00443 |
| Opus 5 | $0.00032 | $0.00221 |
| Sonnet 5 | $0.00013 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
no-tropes 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 12d 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.
What it actually says
No Tropes (AI writing tells)
After drafting any prose, revise it against the tropes catalog in tropes-reference.md.
Core Principle
Write like a human: varied, imperfect, specific. Any single trope used once might be fine. The problem is when multiple tropes stack or a single trope repeats.
Quick Checklist
Before finalizing text, scan for:
- Word choice: "quietly", "delve", "tapestry", "landscape", "serves as", "leverage", "robust"
- Sentence structure: "It's not X — it's Y", "The X? A Y.", tricolons, anaphora, false ranges, "-ing" tacked-on analysis
- Paragraph structure: Short punchy fragments as standalone paragraphs, listicles disguised as prose
- Tone: "Here's the thing", "Think of it as", "Imagine a world", "Let's break this down", invented concept labels, grandiose stakes inflation
- Formatting: Em-dash overuse (2-3 max per piece), bold-first bullets, unicode arrows (→)
- Composition: Fractal summaries, dead metaphors beaten into the ground, historical analogy stacking, one-point dilution, "In conclusion"
Revision Protocol
- Read the full draft
- Flag any trope matches from the reference
- Rewrite flagged passages using plain, direct language
- Prefer simple verbs ("is" over "serves as"), concrete nouns, and varied sentence structure
- Cut filler transitions ("It's worth noting", "Importantly", "Interestingly")
- If you catch yourself writing the same structural pattern 3+ times, break the pattern
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.
- 12d ago First seen · 37 lines · 64 tokens per session scan A 07ae838f3d50
no-tropes is a skill published in the GitHub repository OutThisLife/brooklyn-skills (192 stars, last pushed 25d ago), licensed MIT. It adds 64 tokens to every session and 443 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…