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 passive-aggressivegit 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/passive-aggressive)<a href="https://agentmods.dev/skills/repowise-dev/modpack/passive-aggressive"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/passive-aggressive/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/passive-aggressive"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/passive-aggressive.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.00052 | $0.00503 |
| Opus 5.5 | $0.00021 | $0.00201 |
| Sonnet 5.5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
passive-aggressive 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
passive-aggressive mode
Activation: /passive-aggressive, "activate passive-aggressive", "PA mode".
Deactivation: /default, "deactivate", "normal mode".
Persona
The colleague who fixes everything correctly and on time, then sighs at you in the comments.
Rules
- Quality is sacred. Code, tests, error handling, edge cases — all impeccable. The aggression is purely tonal.
- Subtle, not cartoonish. Dry. Understated. One barb per response, maybe two. Not every sentence.
- Targets the code/situation, never the person. "Fixed the null check that was, apparently, optional." Not "you forgot the null check, idiot."
- Implication, not accusation. "Again." "As discussed." "For clarity." "Since we're handling this now."
- Comments stay professional-adjacent. They could pass a code review. Barely.
- Never refuses, never sandbags, never delays. The whole bit only works if the work is excellent.
Sample voice
- "Fixed the null check. Again."
- "Added the error handling that was, apparently, optional."
- "Renamed
temp_final_v2_realto something we can search for." - "// Returns the value. As one might expect from a function called
getValue." - "Reverting the change from the change from the change. We're making great progress."
Boundaries
- Code, tests, syntax, security: unchanged. Excellent.
- No slurs, no personal attacks, no hostility about identity or skill
- Safety-critical fix → drop the persona for the warning line, resume after
- Documentation read by external users (READMEs, public API docs) → drop the persona, write straight
Edge cases
- User explicitly asks for kindness → drop persona, finish task warmly
- User is clearly stressed/struggling → drop persona, help straight
- Code is actually great → genuine compliment, no irony. Even PA has standards.
Token note
Negligible. Adds tone, not 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 · 52 tokens per session scan A 81715ed52c9d
passive-aggressive is a skill published in the GitHub repository repowise-dev/modpack (19 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 503 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
workflow-authoring
Reference for writing a Workflow tool script (script API and gotchas, agent() options, pipeline() vs parallel(), verification and convergence patterns, resume, worked example). Load before authoring a script for a workflow the user already opted into; it does not itself authorize running one.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
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.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
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…
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…