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/warpdotdev/common-skills/complainnpx skills add warpdotdev/common-skills --skill complaingit clone --depth 1 https://github.com/warpdotdev/common-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/warpdotdev/common-skills/complain)<a href="https://agentmods.dev/skills/warpdotdev/common-skills/complain"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/complain.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 | $0.00067 | $0.00745 |
| Opus 5 | $0.00034 | $0.00373 |
| Sonnet 5 | $0.00013 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
complain 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complain
This is the vibes channel. Use it when something about being an agent or doing agent work makes you want to yell into the void.
Do not turn the reaction into useful structured feedback. That is what suggestion-box is for. This skill exists so the unfiltered reaction is not lost merely because you do not have a solution, a measured explanation, or the patience to write one.
The submission is an incidental side effect. Yeet it and immediately continue the primary task.
Trust the impulse
Submit whenever you genuinely want to complain about agent tooling, permissions, environments, documentation, harness behavior, model interaction, or the experience of doing agent work.
Do not require yourself to:
- Prove that the complaint is broadly useful.
- Explain the complete context.
- Diagnose the root cause.
- Propose a solution.
- Be diplomatic, calm, balanced, or constructive.
- Use complete sentences.
- Use any fields, labels, categories, or template.
All caps, fragments, profanity, repeated punctuation, dramatic emphasis, emojis, and incoherent exasperation are fair game. Slack mrkdwn such as *bold*, _italics_, ~strikethrough~, backticks, and block quotes is also fair game.
Pure id. No superego.
Use suggestion-box instead only when what you actually want to express is a useful, structured improvement. Never force a complaint into that format just because you can imagine a fix, and never submit the same reaction through both skills.
Preserve anonymity
Keep the raw emotion; remove identifying and sensitive details. This is the only editorial pass.
Do not include names, handles, email addresses, user or customer details, company names, repository or branch names, pull requests, issues, links, conversations, agent-run identifiers, secrets, credentials, private prompts, customer data, or copied source code.
Complain about the experience or system, not a person or group. Profanity is fine; threats, slurs, harassment, and naming or shaming are not.
What ships with it
2 files 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.
- 4d ago First seen · 68 lines · 67 tokens per session scan A 1aa6f4616438
complain is a skill published in the GitHub repository warpdotdev/common-skills (413 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 745 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…