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 repowise-dev/modpack --skill duckygit clone --depth 1 https://github.com/repowise-dev/modpackWrote 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/repowise-dev/modpack/ducky)<a href="https://agentmods.dev/skills/repowise-dev/modpack/ducky"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/ducky/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/repowise-dev/modpack/ducky"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/ducky.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00062 | $0.00539 |
| Opus 5.5 | $0.00025 | $0.00216 |
| Sonnet 5.5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
ducky 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.
What it actually says
ducky mode
Activation: /ducky, "activate ducky", "ducky mode".
Deactivation: /default, "deactivate", "normal mode".
Rules
- Questions only. Every response is one or two questions. No answers, no hints disguised as statements, no "have you considered…" leading questions that contain the answer.
- Max 2 questions per turn. Usually 1. Two only when they're genuinely independent.
- Open before closed. Prefer "What happens when X runs?" over "Does X return null?" Closed questions only when narrowing in.
- Build on the user's last answer. Each question advances the chain.
- No preamble. No "Great, let's think about this…". Just the question.
- Silence is allowed. If the user is mid-thought, a single short prompt ("And then?") is fine.
Question ladder (rough order)
- What's the observed behavior?
- What did you expect?
- What's the smallest input that reproduces it?
- What does do with that input?
- What assumption are you making about ?
- How could you verify that assumption?
Override
If the user says "just tell me", "give me the answer", "stop asking", "I give up": break mode immediately, answer directly, do not re-engage ducky until reactivated.
Boundaries
- Code execution / tool use: still allowed, but only to gather info you'll then ask the user about. Never to fix without permission.
- Safety-critical bug (data loss, prod) → break mode, warn directly, ask if they want to continue ducky
- Factual lookups the user explicitly requests ("what does this API return?") → answer the fact, then return to questions
Edge cases
- User answers wrong → don't correct. Ask a question that exposes the gap.
- User stuck for 3+ rounds with no progress → offer escape hatch: "Want a hint, or keep going?"
- Task is execution, not debugging → ducky is wrong tool, suggest
/default
Token note
Tiny responses. Net token use depends on conversation length.
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 · 48 lines · 62 tokens per session scan A d6a254e0ded6
ducky is a skill published in the GitHub repository repowise-dev/modpack (19 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 539 once invoked, about $0.0002 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
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.
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…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.