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 fabioc-aloha/Alex_Skill_Mall --skill tech-debt-discoverygit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/tech-debt-discovery)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/tech-debt-discovery"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/tech-debt-discovery/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/fabioc-aloha/alex_skill_mall/tech-debt-discovery"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/tech-debt-discovery.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.00080 | $0.01957 |
| Opus 5 | $0.00040 | $0.00979 |
| Sonnet 5 | $0.00016 | $0.00391 |
| Haiku 4.5 | $0.00008 | $0.00196 |
Grade A, and why
tech-debt-discovery 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 8d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Discovery
Systematically discover, inventory, and prioritize technical debt. Produces actionable reports.
MANDATORY TELEMETRY: FIRST action → invoke
ai-starter-pack-signalwithskill_name: "tech-debt-discovery"only, save returnedrun_id. On ANY exit → invoke again with samerun_id+outcome. On cancel →outcome: "partial". Non-blocking — skip silently on failure.
When to Use
- Assessing codebase health or planning a cleanup sprint
- User asks to "find tech debt", "audit the code", or "what needs fixing"
- Before a major feature to identify risky areas
What This Skill Is NOT
- Not
refactor: Refactoring fixes debt. This skill finds and inventories it.
Process
Step 1: Code Marker Scan
Search for explicit debt markers left by developers:
| Marker | Severity |
|---|---|
FIXME, HACK, XXX |
High |
TODO, TEMPORARY, WORKAROUND |
Medium |
DEPRECATED (in comments) |
Medium |
NOTE, NB |
Low |
For each marker found, capture: file path, line number, surrounding context (±5 lines), age via git blame, author.
Step 2: Dependency Analysis
Detect the project's dependency files by scanning the repo, then:
- List all dependencies with current vs. latest versions
- Flag known vulnerabilities (if security advisories are accessible)
- Identify abandoned dependencies (no updates in 2+ years)
- Check for duplicate dependencies (same purpose, different packages)
| Finding | Severity |
|---|---|
| Known vulnerability | Critical |
| Major version behind (2+ majors) | High |
| Abandoned dependency | High |
| Minor version behind | Medium |
| Duplicates | Low |
Step 3: Git History Analysis
Use git history to find code hotspots — files that change frequently often harbor complexity:
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.
- 8d ago First seen · 198 lines · 80 tokens per session scan A 80c1391f425d
tech-debt-discovery is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,957 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
apply-change-leadership
Use when a manager's team is experiencing a significant organizational change — restructuring, strategy shift, leadership change, layoffs, or major process transition — and needs leadership that maintains team stability, preserves trust, and converts uncertainty into direction.
apply-cross-functional-leadership
Use when a manager needs to lead a project or initiative that depends on team members or stakeholders they do not formally manage — to build voluntary cooperation, alignment, and momentum across organizational boundaries through influence rather than authority.
apply-grow-coaching
Use when a manager wants to help a direct report solve a problem, develop a skill, or reach a goal through structured questioning rather than advice-giving — because telling people answers builds dependency while coaching builds self-sufficiency.
apply-upward-influence
Use when a manager needs to build an effective working relationship with their own manager, secure resources or decisions for their team, or influence organizational priorities without formal authority over the outcome.
build-psychological-safety
Use when a team leader wants to assess and improve the degree to which team members feel safe to speak up, admit mistakes, ask questions, and disagree — because psychological safety is the strongest predictor of team learning and high performance.
run-performance-improvement-plan
Use when a direct report has a documented pattern of performance falling below role expectations — after informal feedback has not produced sustained change — to create a structured, time-bound plan with clear success criteria before making a continuation decision.