skilld
All skills
softaworks avatar

/reducing-entropy

@1c0662a
by softaworkssoftaworks/agent-toolkit2.5k stars
230

Manual-only skill for minimizing total codebase size. Only activate when explicitly requested by user. Measures success by final code amount, not effort. Bias toward deletion.

Ask your Agent

Use this Skill: https://skilld.dev/gh/softaworks/agent-toolkit/reducing-entropy

This session only. Nothing lands on disk.

referencesexpensive-to-add-later.md

≈625 tokens on demand. Your agent reads this file only when SKILL.md points to it.

PAGNI: Probably Are Gonna Need It

The Core Insight

"When should you override YAGNI? When the cost of adding something later is so dramatically expensive compared with the cost of adding it early on that it's worth taking the risk."

YAGNI is a good default. But some things are genuinely cheaper to build in from the start than to retrofit later. Know the difference.

Why This Matters

Ruthless YAGNI application can backfire when:

  • Adding it later requires touching everything (logging, timestamps, audit trails)
  • You can't add it retroactively at all (API versioning, mobile app kill switches)
  • The cost of not having it is catastrophic (security fundamentals, data you threw away)

The avoiding-complexity skill pushes toward less. This mindset identifies the exceptions where "add it now" beats "add it later."

Common PAGNIs

Data you can't get back:

  • created_at / updated_at timestamps on every table
  • Audit logs (who did what when)
  • Many-to-many from the start if there's any hint you'll need more than one

Infrastructure that's painful to retrofit:

  • API versioning (even if v1 is the only version)
  • API pagination (even if lists are small now)
  • Automated deploys and CI from day one
  • Logging infrastructure

Security fundamentals:

  • Vulnerability disclosure policy and security@ email
  • Session/password invalidation mechanisms
  • Safe ways to move redacted data out of production

The Test

Before invoking PAGNI, ask:

  1. Is retrofitting dramatically more expensive? (10x+, not 2x)
  2. Is this a known pattern from experience? (not speculative)
  3. Is the cost of adding it now actually low? (minutes/hours, not days)

If yes to all three, it's a PAGNI. Otherwise, YAGNI still applies.

The Balance

PAGNI is not an escape hatch for over-engineering. It's a small, specific list of exceptions learned from painful experience. When in doubt, YAGNI wins.

Most features: YAGNI. Infrastructure and data collection: probably PAGNI.

External References

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides a framework for reducing code complexity through deletion and simplification. It is conceptually safe but carries a low risk of indirect prompt injection, as it requires the agent to analyze and modify external codebases that could contain malicious instructions designed to trick the agent into removing security controls.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    7 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 1c0662a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 9 months ago

Topics

  • Refactoring
  • entropy
  • code-deletion
  • codebase-size
  • minimalism
  • technical-debt
  • architecture

README badge

README badge for softaworks/agent-toolkit/reducing-entropy

What it does

Reduces total codebase size by favoring deletion over addition, measuring success by final code amount rather than effort or refactoring elegance. Requires explicit user activation and loading a reference mindset before proceeding; applies to any project where minimizing lines of code is the primary goal, not organizational improvements.

Generated from the current SKILL.md.

Frequently asked

When should I activate this skill?
Only when explicitly requested by the user. This is a manual-only skill for focused reduction efforts, not a default mode.
What does 'success' mean for this skill?
Success is measured by final codebase size, not effort or refactoring cleanliness. Writing 50 lines to delete 200 lines is a win.
Does this skill apply to all codebases?
No. Skip it if the codebase is already minimal, if you're constrained by framework conventions or regulatory requirements, or if reduction isn't the stated goal.
How do I use the reference mindsets?
Load at least one mindset from the references/ directory before proceeding. Read the frontmatter descriptions to find which applies, then state which you loaded.

Generated from the current SKILL.md. These answers refresh after source changes.