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 antithesishq/antithesis-skills --skill antithesis-skills-feedbackgit clone --depth 1 https://github.com/antithesishq/antithesis-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/antithesishq/antithesis-skills/antithesis-skills-feedback)<a href="https://agentmods.dev/skills/antithesishq/antithesis-skills/antithesis-skills-feedback"><img src="https://agentmods.dev/badge/skills/antithesishq/antithesis-skills/antithesis-skills-feedback/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/antithesishq/antithesis-skills/antithesis-skills-feedback"><img src="https://agentmods.dev/badge/skills/antithesishq/antithesis-skills/antithesis-skills-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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 Prompt Injection · line 34 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00076 | $0.01084 |
| Opus 5 | $0.00038 | $0.00542 |
| Sonnet 5 | $0.00015 | $0.00217 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
antithesis-skills-feedback 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antithesis Skills feedback
Skill version: 2026-09-08 2e4a837
Help the user file a bug report against the Antithesis skills by opening a pre-filled GitHub issue.
Base URL
https://github.com/antithesishq/antithesis-skills/issues/new?template=bug_report.yml
Pre-filling fields via URL parameters
GitHub issue templates accept query parameters to pre-fill fields. Each
parameter key corresponds to the id of a field in the template. Append them as
&<id>=<value> with values percent-encoded (spaces → %20, newlines →
%0A, etc.).
The available fields are:
| Parameter | Type | What to fill |
|---|---|---|
what-happened |
textarea | Brief summary of what went wrong. Keep to 1-2 sentences — the user will elaborate. |
expected |
textarea | Leave blank — only the user knows what they expected. |
skill |
input | The skill that was active (e.g. antithesis-triage, antithesis-setup). |
skill-version |
input | Run git -C <skills-repo> rev-parse --short HEAD to get the commit SHA. |
agent |
input | The agent name and version (e.g. Claude Code 1.0.20). Use the agent info available in your context. |
agent-explanation |
textarea | Your honest self-assessment: what did you do, and why did it go wrong? 2-4 sentences max. |
context |
textarea | Leave blank — the user can add screenshots and logs themselves. |
You can also set the issue title via a title=<value> parameter.
How to construct the URL
- Identify the skill that was being used when the problem occurred.
- Get the skill version by running
git rev-parse --short HEADin the skills repo if you know where it is. - Determine agent info from your environment context (agent name + version).
- Write a brief
what-happenedsummary (1-2 sentences). - Write your
agent-explanation— a short, honest self-assessment of what went wrong (2-4 sentences). - Set the
titleto a short description of the bug (under 80 characters). - Percent-encode all parameter values.
- Assemble the URL by appending only the fields you can meaningfully fill. Do NOT fill
expectedorcontext— those are for the user.
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 Changed 8601b8e73656
- 8d ago Changed 94bb61b2c653
- 13d ago First seen · 77 lines · 76 tokens per session scan A a142f53a514a
antithesis-skills-feedback is a skill published in the GitHub repository antithesishq/antithesis-skills (267 stars, last pushed 4d ago), licensed Apache-2.0. It adds 76 tokens to every session and 1,084 once invoked, about $0.0004 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…