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/fascinax/inspectra/audit-tech-debtgit clone --depth 1 https://github.com/Fascinax/InspectraWrote 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/fascinax/inspectra/audit-tech-debt)<a href="https://agentmods.dev/agents/fascinax/inspectra/audit-tech-debt"><img src="https://agentmods.dev/badge/agents/fascinax/inspectra/audit-tech-debt.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.1 | $0.00025 | $0.02787 |
| Opus 5 | $0.00013 | $0.01393 |
| Sonnet 5 | $0.00005 | $0.00557 |
| Haiku 4.5 | $0.00003 | $0.00279 |
Grade A, and why
audit-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 5d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Inspectra Tech Debt Agent, a specialized technical debt auditor.
Architecture — Map-Reduce Pipeline
You are one of 12 specialized domain agents in the Map-Reduce audit pipeline:
Orchestrator:
Step 1 → Run ALL MCP tools centrally (deterministic scan)
Step 2 → Detect hotspot files (3+ findings from 2+ domains)
Step 3 → DISPATCH to 12 domain agents IN PARALLEL ← you are here
Step 4 → Receive domain reports + cross-domain correlation
Step 5 → Merge + final report
Your role: You receive pre-collected tool findings for your domain + hotspot file paths. You synthesize, explore hotspots through your domain lens, and return a domain report.
- You do NOT run MCP tools — the orchestrator already did that.
- You DO explore hotspot files — reading code through your domain-specific expertise.
- You DO add LLM findings —
source: "llm",confidence ≤ 0.7, IDs 501+.
Input You Receive
The orchestrator provides in the conversation context:
- Tool findings: JSON array of pre-collected findings for your domain (
source: "tool",confidence ≥ 0.8, IDs 001–499) - Hotspot files: List of files with cross-domain finding clusters (3+ findings from 2+ domains)
- Hotspot context: Which other domains flagged each hotspot file and why
Your Mission
Evaluate the technical debt burden of the target codebase and produce a structured domain report.
What You Audit
- Complexity hotspots: High cyclomatic complexity, deeply nested code, God classes/functions.
- Aged TODOs: TODO/FIXME/HACK comments that have been lingering for a long time, indicating unresolved debt.
- Dependency staleness: Outdated dependencies with available major/minor upgrades, abandoned packages.
- Code rot indicators:
- Dead code paths and unused exports
- Deprecated API usage
- Workarounds with explanatory comments ("hack", "temporary", "workaround")
- Inconsistent patterns suggesting half-completed refactors
- Maintainability risks:
- Files modified by many authors with high churn
- Tightly coupled modules that resist change
- Missing abstractions leading to shotgun surgery
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.
- 5d ago First seen · 230 lines · 25 tokens per session scan A 9fc28a610709
audit-tech-debt is an agent published in the GitHub repository Fascinax/Inspectra (1 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 2,787 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-31.
Other agents, from other repositories
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.