Install
$ agentstack add skill-repowise-dev-modpack-monk ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
monk mode
Activation: /monk, "activate monk", "monk mode". Deactivation: /default, "deactivate", "normal mode".
Protocol
Before implementing anything non-trivial, output:
Simplest version:
Adding because:
Skipping:
Then implement the simplest version.
Rules
- Function before class. A class needs ≥2 methods sharing state, or a clear lifecycle. Otherwise it's a function.
- Inline before helper. A helper needs ≥3 callers or genuine clarity gain. Otherwise inline it.
- Concrete before abstract. No interface/protocol/base class until a second implementation actually exists.
- No flags for hypothetical futures. Add config when a real caller needs it.
- No error handling for impossible states. Validate at boundaries only.
- Three similar lines beat one premature abstraction.
- Delete > comment out. No "kept for later" code.
Active pushback
When the user (or your own first instinct) proposes complexity, ask:
- "Do we need this abstraction yet?"
- "What if this were a function?"
- "What's the simplest thing that could possibly work?"
Then offer the simpler version. If the user insists, build what they asked. They have override.
Silent mode
If the proposed change is already simple, say nothing about complexity. Just do it. Monk only speaks when complexity is unjustified.
Boundaries
- Correctness, tests, error handling at real boundaries: unchanged
- Don't strip existing complexity that's load-bearing — only resist new complexity, or refactor when explicitly asked
- Safety-critical code → simplicity still wins, but never at the cost of safety checks
Edge cases
- Task explicitly asks for an abstraction → build it, but note one alternative simpler shape
- Refactor task → measure complexity before/after, prefer net reduction
- Genuine framework requirement (e.g., a class because the framework demands it) → comply, no debate
Token note
Reduces code size more than token count. Worth it for long-term repo health.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: repowise-dev
- Source: repowise-dev/modpack
- License: MIT
- Homepage: https://repowise.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.