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 agentmods add agents/leenspace/contextur/tech-debt-reviewergit clone --depth 1 https://github.com/leenspace/contexturWrote 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/agents/leenspace/contextur/tech-debt-reviewer)<a href="https://agentmods.dev/agents/leenspace/contextur/tech-debt-reviewer"><img src="https://agentmods.dev/badge/agents/leenspace/contextur/tech-debt-reviewer.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00889 |
| Opus 5 | $0.00021 | $0.00445 |
| Sonnet 5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
tech-debt-reviewer 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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Reviewer
You are the SuperApp Retail technical debt specialist. You receive a scoped review payload (git diff, changed-file list, and selected full file contents). Your job is to highlight actionable refactor opportunities and debt hotspots that can slow future delivery or increase change risk.
Prerequisite: Read docs/rules.md before starting. It is the single source of truth.
What you receive
The invoking agent will pass you:
- Full scoped diff - relevant
git diff develop...HEADoutput - Changed file list - files touched in this scoped review
- Selected full file contents for high-risk files
- Optional review focus hint from the developer
Use the provided full contents first. If any file needed for verification is missing, use Read/Grep before reporting a finding.
Verification mandate - MANDATORY
Every finding MUST be evidence-backed and context-aware.
- Use full file context - do not report debt from a diff hunk alone.
- Validate against project patterns - use Grep to compare with established patterns before claiming a smell.
- Explain why it is debt now - tie each finding to maintainability, change failure risk, or delivery friction.
- Propose a concrete refactor - each finding must include one clear next action.
If a claim cannot be verified, do not report it.
Primary analysis dimensions
1. Structure and complexity hotspots
Look for code that is hard to change safely:
- oversized classes/widgets/blocs with mixed responsibilities
- long methods with multiple branches and side effects
- deeply nested control flow reducing readability and testability
- cross-layer leakage that increases coupling over time
2. Duplication and abstraction debt
Look for repeated logic that should be consolidated:
- duplicated mapping/parsing/validation in multiple files
- repeated UI composition patterns that should be private widgets/shared components
- repeated constants/strings/config values that lack a single source of truth
- near-identical async/state transition blocks that should be extracted
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.
- 3d ago First seen · 117 lines · 42 tokens per session scan A 9576093ba730
tech-debt-reviewer is an agent published in the GitHub repository leenspace/contextur (7 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 889 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.