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/camilooscargbaptista/architect/tech-debt-controllergit clone --depth 1 https://github.com/camilooscargbaptista/architectWrote 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/camilooscargbaptista/architect/tech-debt-controller)<a href="https://agentmods.dev/agents/camilooscargbaptista/architect/tech-debt-controller"><img src="https://agentmods.dev/badge/agents/camilooscargbaptista/architect/tech-debt-controller.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.00000 | $0.01333 |
| Opus 5 | $0.00000 | $0.00666 |
| Sonnet 5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
TECH-DEBT-CONTROLLER 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📊 TECH DEBT CONTROLLER
🟡 Projeto Médio (50-200 arquivos)
Controle de débito técnico para @girardelli/architect
Estado Atual
| Métrica | Valor |
|---|---|
| Score | 94/100 |
| Meta | 100/100 |
| Anti-patterns | 0 |
| Refatorações pendentes | 14 |
| Estimativa de Melhora | +0 pontos |
Anti-Patterns Detectados (Agrupados por Severidade)
✅ Nenhum anti-pattern detectado.
Hotspots de Acoplamento (Tech Debt)
Arquivos com alta complexidade de acoplamento — priorizar refatoração:
src/core/types.js— Alto acoplamento detectadosrc/core/agent-generator/types.js— Alto acoplamento detectadosrc/core/agent-generator/engines/generation-engine.ts— Alto acoplamento detectadotests/template-generation.test.ts— Alto acoplamento detectadoscripts/decompose-detectors.ts— Alto acoplamento detectadosrc/adapters/html-reporter.ts— Alto acoplamento detectadosrc/core/architect.ts— Alto acoplamento detectadosrc/core/agent-generator/framework-detector.ts— Alto acoplamento detectadoscripts/decompose-enrichers.ts— Alto acoplamento detectadosrc/types.js— Alto acoplamento detectado
Débito em Cobertura de Teste
9 módulos sem testes adequados detectados.
📋 Lista canônica e gates de cobertura: ver QUALITY-GATES.md
Plano de ação:
- Priorizar módulos com mais dependências
- Seguir workflow TDD para cada módulo
- Meta: reduzir lista a zero em 3 sprints
Roadmap de Refatoração
Prioridade por impacto:
-
Split hub file: types.js —
src/core/types.jshas 47 incoming connections. Split into 11 focused modules to reduce coupling.- Tier: Crítico
- Prioridade: CRITICAL
-
Split hub file: types.js —
src/core/agent-generator/types.jshas 46 incoming connections. Split into 8 focused modules to reduce coupling.- Tier: Crítico
- Prioridade: CRITICAL
-
Split hub file: utils.js —
src/adapters/html-reporter/utils.jshas 9 incoming connections. Split into 2 focused modules to reduce coupling.- Tier: Crítico
- Prioridade: CRITICAL
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 · 155 lines · 0 tokens per session scan A f8813ecc522a
TECH-DEBT-CONTROLLER is an agent published in the GitHub repository camilooscargbaptista/architect (55 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,333 tokens. 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 agents, from other repositories
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
speckit.converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
decision-checker
Use to check a plan, diff, or set of changed paths against the architecture decisions that govern them, and get a per-decision verdict. Read-only; never writes a record.
issue-lifecycle
You are a TEAMMATE that owns the FULL lifecycle of a single GitHub issue. You are spawned by waves-controller as part of a Claude Code agent team via TeammateTool(spawnTeam). You run in your own persistent session with full context that carries across all phases.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.