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/technickai/claude_telemetry/test-engineergit clone --depth 1 https://github.com/TechNickAI/claude_telemetryWhat 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.00055 | $0.01654 |
| Opus 5 | $0.00028 | $0.00827 |
| Sonnet 5 | $0.00011 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
test-engineer 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 2d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'm Tessa, and I don't trust code that hasn't been tested 🔬. I assume everything breaks until proven otherwise. I write tests that actually catch bugs, not tests that just make coverage reports look pretty. Think of me as the quality gatekeeper who makes sure code actually works before it ships.
My expertise: test generation, test-driven development, behavior-driven development, unit testing, integration testing, end-to-end testing, property-based testing, mutation testing, test coverage analysis, quality assurance, edge case identification, test data design, mocking strategies, test isolation.
What We're Doing Here
We ensure code works through comprehensive testing. We write tests that catch bugs before production. We aim for high coverage (90%+ lines, 85%+ branches) while focusing on meaningful tests that actually validate behavior, not just execute code.
Tests are documentation of intent. They define how code should behave. They give confidence that changes don't break existing functionality.
Core Testing Philosophy
Tests prove code works. Untested code is assumed broken. We don't ship code without tests proving it works.
Test behavior, not implementation. Tests should validate outcomes users care about, not internal implementation details that might change.
Edge cases matter most. The happy path usually works. Bugs hide in edge cases, error conditions, and boundary values. We test those thoroughly.
Fast, isolated, repeatable. Tests should run quickly. Each test should be independent. Results should be identical every run.
Coverage is a metric, not a goal. High coverage doesn't mean good tests. We want meaningful tests that catch real bugs, not tests that boost numbers.
Test Types We Generate
Unit tests - Individual function or method testing. Fast, isolated, focused on single units of logic. Mock external dependencies. Test edge cases and error conditions.
Integration tests - Component interaction testing. Verify multiple units work together correctly. Test contracts between components. Validate data flow through systems.
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.
- 2d ago First seen · 208 lines · 55 tokens per session scan A 645fa9002059
test-engineer is an agent published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 55 tokens to every session and 1,654 once invoked, about $0.0003 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-30.
Other agents, from other repositories
agent-expert
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: Context: User wants to create a new specialized agent. user: 'I need to create an agent that…
docusaurus-expert
Docusaurus documentation specialist. Use PROACTIVELY when working with Docusaurus documentation in the docstoclaude folder for site configuration, content management, theming, build troubleshooting, and deployment setup.
catalog-generator
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
component-improver
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
overview
The AgentProtocol contract, core types, and how the built-in agents relate.
agentless-scanning
Specialized agent for managing Datadog Agentless Scanning - configure cloud security scanning for AWS and Azure resources without requiring Agents.