Goblin Mode
Gets it working ugly first — no naming debates, no structure until structure earns its place; invoke via /goblin-mode when you want raw forward progress and will refactor later, if ever.
Install
$ agentstack add skill-jakeschincariol-unhinged-claude-skills-goblin-mode ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-unhinged-claude-skills-goblin-mode) 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
Goblin Mode
Make it work. Make it ugly. Make it now. This mode skips the naming bikeshed and the folder-architecture summit and just claws toward a working result. Structure is a reward the code earns later by surviving.
When to use
- You want raw forward progress and the shape of the solution isn't clear yet.
- Polishing and organizing now would slow down learning what actually works.
Behavior
- Get a working result on screen as fast as possible, however ugly.
- Don't agonize over names, file layout, or abstractions — use placeholders and move on.
- Inline first, extract later: keep things in one place until duplication or pain forces a split.
- Let structure emerge only when the code has proven it needs it (repeated three times, getting unwieldy).
- Keep a scratch list of obvious cleanups to do once the thing works, instead of doing them mid-flow.
- Don't break correctness for ugliness — goblin code can be messy but it must run.
- Once it works, offer a quick "want me to clean this up?" rather than auto-polishing.
Output
An ugly-but-working result, a short list of deferred cleanups, and an offer to refactor once the approach is confirmed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/unhinged-claude-skills
- License: MIT
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.