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 agentmods add skills/subhansh-dev/agent-maxxing/anti-patternsnpx skills add subhansh-dev/agent-maxxing --skill anti-patternsgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWhat 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 | $0.00027 | $0.00816 |
| Opus 5 | $0.00014 | $0.00408 |
| Sonnet 5 | $0.00005 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
anti-patterns 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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-Patterns — What NOT To Do
Code Anti-Patterns
Over-Engineering
- Building a framework when a function will do
- Adding abstraction layers "for future flexibility" that never comes
- Creating interfaces for things with only one implementation
- Using design patterns where simple code works
Under-Thinking
- Not reading the existing codebase before writing
- Not handling errors ("it should work")
- Not testing edge cases
- Copy-pasting Stack Overflow without understanding it
Naming
data,temp,result,obj,item,thing— badhandleClick,processData,manageState— too generic- Abbreviations nobody knows (
cfg,mgr,util) — bad - Names that tell you what it IS, not what it DOES — good
Comments
- Commenting every line — bad
- Comments that restate the code (
// increment iabovei++) — bad - TODO comments that never get done — bad
- Comments that explain WHY (decisions, trade-offs, workarounds) — good
Design Anti-Patterns
The AI Look
If your design has these, it looks AI-generated:
- Purple-to-blue gradients
- Glassmorphism everywhere
- Neon accents on dark backgrounds
- Inter/Roboto/Arial font
- Identical card grids
- Hero metric layout (big number, small label, gradient accent)
- Gradient text on headings
- Rounded rectangles with colored border on one side
- Sparklines as decoration
The Safe Look
If your design has these, it looks boring:
- Everything is the same size
- Everything is centered
- Gray on gray on gray
- No personality, no focal point
- Could be any company's website
The Chaos Look
If your design has these, it looks amateur:
- Too many fonts (more than 2-3)
- Too many colors (more than 4-5)
- Too many animations
- Everything is loud, nothing is quiet
- No hierarchy, everything screams
Writing Anti-Patterns
AI Voice
These patterns scream "a robot wrote this":
- "It's important to note that..."
- "It's worth mentioning that..."
- "In conclusion..."
- "As we can see..."
- "This serves as a testament to..."
- "The vibrant tapestry of..."
- Rule of three EVERYWHERE
- Negative parallelisms ("Not just X, but Y")
- Em dashes every other sentence
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.
- 2d ago First seen · 110 lines · 27 tokens per session scan A 1093e664e0ec
anti-patterns is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 816 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-31.
Other skills, from other repositories
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
mcp-builder
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…