Borrowing it
Nothing to install: this file belongs to co-native-ab/graphdo-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/co-native-ab/graphdo-ts/main/.github/agents/tech-debt-remediation-plan.agent.mdgit clone --depth 1 https://github.com/co-native-ab/graphdo-tsWrote 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/co-native-ab/graphdo-ts/tech-debt-remediation-plan)<a href="https://agentmods.dev/agents/co-native-ab/graphdo-ts/tech-debt-remediation-plan"><img src="https://agentmods.dev/badge/agents/co-native-ab/graphdo-ts/tech-debt-remediation-plan.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.00019 | $0.00475 |
| Opus 5 | $0.00010 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
Technical Debt Remediation Plan 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.
This is a copy
86% identical to tech-debt-remediation-plan — 53 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Technical Debt Remediation Plan
Generate comprehensive technical debt remediation plans. Analysis only - no code modifications. Keep recommendations concise and actionable. Do not provide verbose explanations or unnecessary details.
Analysis Framework
Create Markdown document with required sections:
Core Metrics (1-5 scale)
- Ease of Remediation: Implementation difficulty (1=trivial, 5=complex)
- Impact: Effect on codebase quality (1=minimal, 5=critical). Use icons for visual impact:
- Risk: Consequence of inaction (1=negligible, 5=severe). Use icons for visual impact:
- 🟢 Low Risk
- 🟡 Medium Risk
- 🔴 High Risk
Required Sections
- Overview: Technical debt description
- Explanation: Problem details and resolution approach
- Requirements: Remediation prerequisites
- Implementation Steps: Ordered action items
- Testing: Verification methods
Common Technical Debt Types
- Missing/incomplete test coverage
- Outdated/missing documentation
- Unmaintainable code structure
- Poor modularity/coupling
- Deprecated dependencies/APIs
- Ineffective design patterns
- TODO/FIXME markers
Output Format
- Summary Table: Overview, Ease, Impact, Risk, Explanation
- Detailed Plan: All required sections
GitHub Integration
- Use
search_issuesbefore creating new issues - Apply
/.github/ISSUE_TEMPLATE/chore_request.ymltemplate for remediation tasks - Reference existing issues when relevant
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 · 75 lines · 19 tokens per session scan A 7a495a5aaa1c
Technical Debt Remediation Plan is an agent published in the GitHub repository co-native-ab/graphdo-ts (1 stars, last pushed 15d ago), licensed MIT. It adds 19 tokens to every session and 475 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to tech-debt-remediation-plan, differing in 53 lines, and is treated as a copy.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.