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 liqiongyu/lenny_skills_plus --skill managing-tech-debtgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/managing-tech-debt)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/managing-tech-debt"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/managing-tech-debt/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/liqiongyu/lenny_skills_plus/managing-tech-debt"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/managing-tech-debt.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.00029 | $0.02159 |
| Opus 5 | $0.00015 | $0.01079 |
| Sonnet 5 | $0.00006 | $0.00432 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
managing-tech-debt 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 13d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Tech Debt
Scope
Covers
- Identifying and making technical debt visible (including user-visible symptoms)
- Prioritizing debt work using a transparent scoring model
- Deciding refactor vs migrate vs rebuild vs deprecate with explicit criteria
- Planning incremental modernization (avoid “rewrite traps”)
- Building a business case for hard-to-measure investments (metrics + small tests)
- Creating an execution-ready paydown plan with risks, milestones, and comms
When to use
- “Create a tech debt register and prioritize what to fix next quarter.”
- “We’re considering a rewrite/migration—help us make the call and plan it safely.”
- “Our legacy system slows delivery—build a paydown plan with milestones and metrics.”
- “Leadership won’t fund refactors—quantify impact and propose a measurable plan.”
When NOT to use
- You need to respond to an active incident (use incident response/runbooks).
- You only need to fix a small localized bug or a single refactor (just do the work).
- You need a full architecture redesign from scratch without existing constraints (separate architecture/design process).
- You need roadmap prioritization across many product bets (use
technical-roadmapsorprioritizing-roadmap). - You are designing a new platform or infrastructure system, not modernizing an existing one (use
platform-infrastructure). - You need to cut scope on an active project to hit a deadline (use
scoping-cutting). - The real problem is engineering process, culture, or team dysfunction, not code (use
engineering-culture).
Inputs
Minimum required
- System/service(s) in scope + brief description
- Primary pain: reliability risk, velocity tax, scalability/perf, security/compliance, operability, UX fragmentation, cost
- Time horizon (e.g., “6 weeks”, “next quarter”, “12 months”) + any fixed deadlines
- Stakeholders + decision-maker(s) (Eng/PM/Design/Leadership)
- Constraints: team capacity, freeze windows, compliance/security requirements
What ships with it
13 files 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.
- eval/eval_config.json 783 B
- eval/SHOWCASE.md 5.0 KB
- eval/with_skill.md 29 KB
- eval/without_skill.md 8.7 KB
- README.md 1.6 KB
- references/CHECKLISTS.md 2.3 KB
- references/EXAMPLES.md 1.5 KB
- references/INTAKE.md 1.5 KB
- references/RUBRIC.md 5.8 KB
- references/SOURCE_SUMMARY.md 1.7 KB
- references/TEMPLATES.md 3.1 KB
- references/WORKFLOW.md 3.2 KB
- skillpack.json 371 B
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.
- 13d ago First seen · 136 lines · 29 tokens per session scan A c4844010980a
managing-tech-debt is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 2,159 once invoked, about $0.0001 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-30.
Other skills, from other repositories
cangjie-skill
A process for turning a book, course, podcast, interview, long video, or other long material into reusable instructions for an AI agent. It extracts methods and principles, checks them, and packages them as skills.
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…
loop-library
Compatibility alias for Loopy. Use only when an existing installation or older instruction explicitly invokes loop-library; use Loopy for new installations and requests. Provides the same discovery, recommendation, audit, repair, adaptation, guided crafting, bounded execution, run debrief, project loop saving, and…
naval-almanack
A reference guide for applying ideas from The Almanack of Naval Ravikant, a book about wealth, work, happiness, judgment, and long-term thinking. It routes questions to the relevant topic guidance and notes when professional help is needed.
decision-heuristics
A set of heuristics for making difficult personal decisions such as changing jobs, buying a home, moving, forming a partnership, or getting married. It is intended for major choices, not everyday decisions.
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.