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.
git clone --depth 1 https://github.com/IgniteUI/igniteui-angularWrote 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/igniteui/igniteui-angular/tdd-test-writer-agent)<a href="https://agentmods.dev/agents/igniteui/igniteui-angular/tdd-test-writer-agent"><img src="https://agentmods.dev/badge/agents/igniteui/igniteui-angular/tdd-test-writer-agent/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/igniteui/igniteui-angular/tdd-test-writer-agent"><img src="https://agentmods.dev/badge/agents/igniteui/igniteui-angular/tdd-test-writer-agent.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.01847 |
| Opus 5.5 | $0.00014 | $0.00739 |
| Sonnet 5.5 | $0.00007 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
tdd-test-writer-agent 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 25d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 25d ago Changed · +1 lines 307b6a7928da
- 1mo ago First seen · 183 lines · 35 tokens per session scan A ee2526d74232
tdd-test-writer-agent is an agent published in the GitHub repository IgniteUI/igniteui-angular (599 stars, last pushed today), with no licence file. It adds 35 tokens to every session and 1,847 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-30.
Other agents, from other repositories
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
swe-debugger
Resolves failing type checks, lint findings, and tests one cause at a time, diagnosing each before changing code, keeping pinned behaviour intact, and never suppressing or bypassing a check.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
ci-fixer
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.