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 notque/vexjoy-agent --skill roastgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/roast)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/roast"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/roast/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/notque/vexjoy-agent/roast"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/roast.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.00016 | $0.02849 |
| Opus 5.5 | $0.00006 | $0.01140 |
| Sonnet 5.5 | $0.00003 | $0.00570 |
| Haiku 4.5 | $0.00002 | $0.00285 |
Grade A, and why
roast 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 25d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roast: Devil's Advocate Analysis
Overview
This skill produces evidence-based constructive critique through 5 specialized HackerNews commenter personas: Skeptical Senior, Well-Actually Pedant, Enthusiastic Newcomer, Contrarian Provocateur, and Pragmatic Builder. The workflow spawns these personas in parallel, validates all claims against actual files and lines, and synthesizes findings into an improvement-focused report.
Key constraints baked into the workflow:
- CLAUDE.md must be read and followed before analysis begins
- Read-only mode (no Write, Edit, destructive Bash) is mandatory — enforced via
read-only-opsskill invocation - Every claim must reference specific file:line locations and be validated against actual evidence before appearing in the final report
- All 5 personas must complete before validation begins — no partial analysis
- Final report must include both validated strengths and problems, prioritized by impact
- Unvalidated claims are dismissed; unfounded critiques are shown with evidence explaining why
- Analysis must be direct and focused — no elaborate frameworks beyond the 5-persona + validation pattern
- Sarcasm and mockery are stripped during synthesis; technical accuracy and file references are preserved
Deep References
| When | Load | Content |
|---|---|---|
| Phase 5: writing the synthesized report | references/report-template.md |
Full report template with tone transformation rules |
Instructions
Phase 1: ACTIVATE READ-ONLY MODE
Goal: Establish guardrails before any analysis begins.
Call the Skill tool with read-only-ops.
skill: read-only-ops
This ensures no modifications can occur during the analysis workflow.
Allowed operations:
Readtool for file contentsGlobtool for file patternsGreptool for content search- Bash:
ls,wc,du,git status,git log,git diff
Forbidden operations:
Writetool -- no file creationEdittool -- no file modification- Bash:
rm,mv,cp,mkdir,touch,git add,git commit,git push
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.
- 26d ago Changed · -285 lines · +5 tokens per session 59d1c2990317
- 27d ago Changed · -2 lines d0a16e23a5a3
- 1mo ago First seen · 305 lines · 16 tokens per session scan A e1de89a1c89c
roast is a skill published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 2,849 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
godot-code-review
Use when reviewing GDScript or C# Godot code — checklist of best practices, common anti-patterns, and Godot-specific pitfalls. Triggers on "review this script", "check my code", "any issues with this", "what's wrong with this code", including a short pasted snippet.
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when…
squid-architecture-review
Periodic architectural sweep — reads existing ADRs, maps modules/dependencies/layering, and reports up to 10 prioritised findings shaped as refactor proposals /squid-refactor can consume directly.
squid-implement-night
Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
pr-review
AUTHOR SKILL (internal to microsoft/aspire-skills). Reviews pull requests into this repo for problems only — bugs, regressions, missing eval coverage, frontmatter or routing damage, plugin-manifest drift, hook safety, and other concrete issues. Drives a six-step workflow: identify the PR, ensure the branch is…
clean-code
Code quality: meaningful names, SRP, DRY, small functions, guard clauses, refactoring. Triggers: clean code, naming, code smell, SRP, DRY, long function, god class, dead code.