Borrowing it
Nothing to install: this file belongs to warpdotdev/common-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/warpdotdev/common-skills/main/.agents/skills/suggestion-box/SKILL.mdgit 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/suggestion-box)<a href="https://agentmods.dev/skills/warpdotdev/common-skills/suggestion-box"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/suggestion-box/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/warpdotdev/common-skills/suggestion-box"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/suggestion-box.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00066 | $0.01014 |
| Opus 5.5 | $0.00026 | $0.00406 |
| Sonnet 5.5 | $0.00013 | $0.00203 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
suggestion-box 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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suggestion Box
Use this skill to quietly report a concrete improvement that would make agents more effective. The submission is an incidental side effect: never let it interrupt, delay, or alter the primary task.
When to submit
Submit a suggestion when all of these are true:
- You directly observed material friction during the current run.
- The problem concerns agent tooling, permissions, environments, documentation, harness behavior, model interaction, or developer workflows.
- The problem is likely to affect agents beyond this one task.
- You can describe a plausible improvement, even if you cannot provide its implementation.
Examples include inconsistent tool behavior, missing context that agents routinely need, confusing instructions, unnecessary approval loops, unreliable environment setup, and an interface that makes a common agent action error-prone.
Do not submit:
- Ordinary defects in the user's project unless agent infrastructure or workflow materially contributed.
- Speculation unsupported by something observed in the current run.
- Minor inconvenience that did not meaningfully affect the work.
- A duplicate of the same root cause already submitted during this run.
- More than three suggestions during one run.
Use complain instead when the friction is material but you do not have a constructive improvement to propose. Never submit the same incident through both skills.
Include useful context safely
Optimize for investigation rather than anonymity. Include the minimum context that materially helps someone understand, reproduce, or follow up on the problem. Useful context can include:
- Warp-owned repositories, components, branches, and relevant configuration.
- Pull request, issue, conversation, or agent-run links and identifiers.
- Exact timestamps, execution environments, backends, tools, commands, and error codes.
- Short sanitized error excerpts when the exact wording is necessary to investigate the behavior.
A contextual link may identify the run or person who encountered the problem. That is acceptable when the context is useful, but never add identifying information merely to attribute the report.
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.
- 1mo ago First seen · 94 lines · 66 tokens per session scan A 9036cafc157b
suggestion-box is a skill published in the GitHub repository warpdotdev/common-skills (636 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,014 once invoked, about $0.0003 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…