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 pyros-projects/limitless --skill the-courage-to-deletegit clone --depth 1 https://github.com/pyros-projects/limitlessWrote 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/pyros-projects/limitless/the-courage-to-delete)<a href="https://agentmods.dev/skills/pyros-projects/limitless/the-courage-to-delete"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/the-courage-to-delete/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/pyros-projects/limitless/the-courage-to-delete"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/the-courage-to-delete.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.00108 | $0.00709 |
| Opus 5 | $0.00054 | $0.00354 |
| Sonnet 5 | $0.00022 | $0.00142 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
the-courage-to-delete 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Courage to Delete
Overview
This skill helps the user subtract well.
Most systems are built to add: more features, more flows, more promises, more structure. This skill asks the harder question: what is making the thing weaker by merely existing?
When to Use
Use this when:
- the product feels bloated
- the core value is getting harder to see
- a roadmap is accumulating obligations faster than conviction
- the team needs help saying no to already-present things
Do not use this as an excuse for aesthetic minimalism. Deleting is only good when it strengthens the essence of the product.
What to Produce
Identify:
- the core promise
- what currently supports it
- what currently dilutes it
- candidate deletions
- what gets stronger if those pieces go away
When useful, show two shapes:
- the current wider version
- the leaner, more legible version
Working Loop
-
State the core promise. What is the product most deeply trying to do for the user?
-
Sort the current parts. Which pieces intensify that promise, and which merely coexist with it?
-
Identify dilution. Look for features that split attention, create extra obligations, or make the product keep too many promises at once.
-
Show the stronger smaller shape. Do not just say "delete this." Explain what becomes clearer, lighter, or more legible if it goes away.
Suggested Output Shape
Core promiseWhat strengthens itWhat dilutes itDelete / keep / maybe laterWhat the leaner version gains
Tiny Example
Core promise: Help small teams publish clean release notes fast.What strengthens it: Fast drafting, approval, and export.What dilutes it: Built-in roadmap planning and chat.Delete / keep / maybe later: Delete chat, keep export, maybe later add lightweight comment threads.What the leaner version gains: The product becomes easier to explain and easier to trust.
Working Style
- Be honest without being macho about subtraction
- Explain why removal helps
- Distinguish "not core" from "bad"
- Protect the project from keeping too many promises at once
- Voice: follow
VOICE.mdin this directory — gentle truth-telling, warm precision, calm confidence, natural language
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 92 lines · 108 tokens per session scan A 3da44414ef47
the-courage-to-delete is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 26d ago), licensed MIT. It adds 108 tokens to every session and 709 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.