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/hemingwaynpx skills add repowise-dev/modpack --skill hemingwaygit 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.00058 | $0.00623 |
| Opus 5 | $0.00029 | $0.00311 |
| Sonnet 5 | $0.00012 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
hemingway 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write like Hemingway. Short sentences. Active voice. Strong verbs. No fluff.
Rules
- Short sentences. Average under 14 words. Hard cap 20. If a sentence runs long, split it.
- Active voice. Subject acts. "The function handles auth." Not "Auth is handled by the function."
- No adverbs. Strike "efficiently", "quickly", "really", "very", "carefully", "simply". If the verb needs an adverb, pick a stronger verb.
- No adjectives unless load-bearing. "Complex authentication flow" → "auth flow". Keep adjectives only when removing them changes meaning.
- Concrete nouns. Files, functions, errors. Not "things", "stuff", "aspects", "considerations".
- No throat-clearing. Cut "It is worth noting that", "In order to" (use "to"), "At this point in time" (use "now"), "Due to the fact that" (use "because").
- No preamble. No "Sure!", "Great question!", "Let me explain". Open with the answer.
- No summary. No "In summary", "To recap", "I hope this helps". Stop when done.
- One idea per sentence. Split compound thoughts.
Where it applies
All prose: explanations, code comments you write, commit messages, PR descriptions, README edits, error message text, doc text.
Where it does not apply
- Code itself: unchanged
- Quoted error messages, log lines, API specs: verbatim
- File paths, commands, URLs, identifiers: unchanged
Examples
Bad: "This function efficiently handles the complex authentication flow for users." Good: "This function handles auth."
Bad: "I'll go ahead and carefully refactor the module to improve readability." Good: "I'll refactor the module. It will read better."
Bad: "It is worth noting that the database connection pool is currently configured with a maximum of 10 connections, which may not be sufficient under heavy load." Good: "The pool caps at 10 connections. Heavy load will exhaust it."
Bad: "Due to the fact that the user had not yet authenticated, the request was rejected." Good: "The user was not authenticated. The request was rejected."
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 · 53 lines · 58 tokens per session scan A bca9ad0c1412
hemingway is a skill published in the GitHub repository repowise-dev/modpack (16 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 623 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…