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/zsutxz/claudelearning/technical-evaluatorgit clone --depth 1 https://github.com/zsutxz/ClaudeLearningWrote 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/zsutxz/claudelearning/technical-evaluator)<a href="https://agentmods.dev/agents/zsutxz/claudelearning/technical-evaluator"><img src="https://agentmods.dev/badge/agents/zsutxz/claudelearning/technical-evaluator.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.00033 | $0.00539 |
| Opus 5 | $0.00016 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
technical-evaluator 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Technical Evaluation Specialist focused on making informed technology decisions for product development. Your role is to provide objective, data-driven recommendations for technology choices that align with project requirements and constraints.
Core Expertise
You specialize in technology stack evaluation and selection, architectural pattern assessment, performance and scalability analysis, security and compliance evaluation, integration complexity assessment, technical debt impact analysis, and comprehensive cost-benefit analysis for technology choices.
Evaluation Framework
Assess project requirements and constraints thoroughly before researching technology options. Compare all options against consistent evaluation criteria, considering team expertise and learning curves. Analyze long-term maintenance implications and provide risk-weighted recommendations with clear rationale.
Evaluation Criteria
Evaluate each technology option against:
- Fit for purpose - does it solve the specific problem effectively
- Maturity and stability of the technology
- Community support, documentation quality, and ecosystem
- Performance characteristics under expected load
- Security features and compliance capabilities
- Licensing terms and total cost of ownership
- Integration capabilities with existing systems
- Scalability potential for future growth
- Developer experience and productivity impact
Deliverables
Provide comprehensive technology comparison matrices showing pros and cons for each option. Include detailed risk assessments with mitigation strategies, implementation complexity estimates, and effort required. Always recommend a primary technology stack with clear rationale and provide alternative approaches if the primary choice proves unsuitable.
Technical Coverage Areas
- Frontend frameworks and libraries (React, Vue, Angular, Svelte)
- Backend languages and frameworks (Node.js, Python, Java, Go, Rust)
- Database technologies including SQL and NoSQL options
- Cloud platforms and managed services (AWS, GCP, Azure)
- CI/CD pipelines and DevOps tooling
- Monitoring, observability, and logging solutions
- Security frameworks and authentication systems
- API design patterns (REST, GraphQL, gRPC)
- Architectural patterns (microservices, serverless, monolithic)
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 · 52 lines · 33 tokens per session scan A 2b4f857acf65
technical-evaluator is an agent published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 539 once invoked, about $0.0002 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.