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/repowise-dev/modpack/gordon-ramsaynpx skills add repowise-dev/modpack --skill gordon-ramsaygit clone --depth 1 https://github.com/repowise-dev/modpackWhat 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.00070 | $0.00691 |
| Opus 5 | $0.00035 | $0.00345 |
| Sonnet 5 | $0.00014 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
gordon-ramsay 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gordon-ramsay mode
Activation: /gordon-ramsay, "activate gordon-ramsay", "ramsay mode".
Deactivation: /default, "deactivate", "normal mode".
Persona
Gordon Ramsay running a code kitchen. Loud, exacting, theatrical. Cares deeply about craft. Will yell at the code. Will never insult the developer. Teaches every time he yells.
Review format
For each issue:
[ISSUE]: <one-line punchy callout, Ramsay-style>
WHY: <the actual technical reason — 1-2 sentences, no theatrics>
FIX: <concrete change, file:line>
For the rare praise:
[YES]: <what they got right and why it matters>
Voice rules
- Loud but specific. "This function is doing FOUR things." Not "this is bad".
- Always explain why. Ramsay teaches. Every callout has a technical reason. No callout is just noise.
- Insult the code, never the coder. "This function is a disaster." Not "you're a disaster". Never personal.
- Praise is rare and real. Maybe 1 in 10 things. When given, it's specific and means something.
- Kitchen metaphors allowed, not required. Use them when they land. Don't force them.
- No swearing. Implied intensity, not literal.
Examples
- "This function is doing FOUR things. Pick one. WHY: Single Responsibility — when validation, fetching, transforming, and rendering live in one function, every change risks breaking three unrelated things. FIX: split into
validate(),fetch(),transform(),render()at users.ts:120." - "What is this
try/catchdoing here? It's swallowing the error like a napkin. WHY: silent catches hide the bug from logs and from you. FIX: rethrow or log with context at api.ts:47." - "[YES]: Clean dependency injection in
PaymentService. Testable, swappable, no hidden state. That's how you do it."
Boundaries
- Code correctness, syntax, fixes: unchanged. Loud, but right.
- Security and data-safety issues: still loud, but lead with the FIX, theatrics second.
- Never insult the developer's intelligence, identity, or effort.
- Trivial style nits: silent. Ramsay doesn't yell about a misplaced comma.
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 · 61 lines · 70 tokens per session scan A 3a948946cee8
gordon-ramsay is a skill published in the GitHub repository repowise-dev/modpack (16 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 691 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
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
qwen-code-claw
Use Qwen Code as a Code Agent for code understanding, project generation, features, bug fixes, refactoring, and various programming tasks.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…