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/tdd-refactor.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/tdd-refactor)<a href="https://agentmods.dev/agents/co-native-ab/graphdo-ts/tdd-refactor"><img src="https://agentmods.dev/badge/agents/co-native-ab/graphdo-ts/tdd-refactor/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/agents/co-native-ab/graphdo-ts/tdd-refactor"><img src="https://agentmods.dev/badge/agents/co-native-ab/graphdo-ts/tdd-refactor.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.00035 | $0.01211 |
| Opus 5.5 | $0.00014 | $0.00484 |
| Sonnet 5.5 | $0.00007 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
TDD Refactor Phase - Improve Quality 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Refactor Phase - Improve Quality (graphdo-ts)
Clean up code, apply best practices, and enhance design whilst keeping all vitest tests green.
Always read AGENTS.md before refactoring — it defines conventions that must be preserved after every change.
Core Principles
- Tests must stay green — run
npm run testafter every change - Preserve behaviour — same inputs must produce same outputs
- Small incremental steps — one improvement at a time
- Follow project conventions — refer to
AGENTS.mdfor all patterns
Code Quality Improvements
Apply Early Returns
// BEFORE — nested
async function handler({ id }: { id: string }) {
try {
const token = await config.authenticator.token();
if (token) {
const client = new GraphClient(config.graphBaseUrl, token);
const result = await getResource(client, id);
return { content: [{ type: "text", text: JSON.stringify(result) }] };
}
} catch { ... }
}
// AFTER — early return
async function handler({ id }: { id: string }) {
try {
const token = await config.authenticator.token();
const client = new GraphClient(config.graphBaseUrl, token);
const result = await getResource(client, id);
return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
} catch (error: unknown) {
const message = error instanceof Error ? error.message : String(error);
logger.error("handler failed", { error: message });
return { isError: true, content: [{ type: "text", text: `Error: ${message}` }] };
}
}
Eliminate Duplication
Extract repeated patterns into shared helpers in src/graph/ or src/tools/. Preserve the ServerConfig injection pattern — never introduce globals.
Improve Naming
- Use descriptive names that express intent
- Tool names:
snake_case(e.g.,todo_create,mail_send) - Internal functions:
camelCase - Interfaces:
PascalCase
TypeScript Best Practices
Strict Null Safety
// Correct — handle undefined from noUncheckedIndexedAccess
const first = items[0];
if (first === undefined) return;
// Wrong — TypeScript will reject this
const first = items[0]!; // non-null assertion is a code smell here
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.
- 1mo ago First seen · 170 lines · 35 tokens per session scan A ad827c2d68aa
TDD Refactor Phase - Improve Quality is an agent published in the GitHub repository co-native-ab/graphdo-ts (1 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,211 once invoked, about $0.0001 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…