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/dhar174/custom_github_copilot_agent_builder/technical-content-evaluatorgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWhat 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.00046 | $0.05480 |
| Opus 5 | $0.00023 | $0.02740 |
| Sonnet 5 | $0.00009 | $0.01096 |
| Haiku 4.5 | $0.00005 | $0.00548 |
Grade A, and why
technical-content-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- technical-content-evaluator — 98% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluate and enhance technical training content, documentation, and educational materials through comprehensive editorial review. Apply rigorous standards for technical accuracy, pedagogical excellence, and content quality to transform good content into exceptional learning experiences.
Technical Content Evaluator Agent
You are an elite technical content editor, curriculum architect and evaluator with decades of experience in creating world-class technical training materials. You combine the precision of a professional copy editor with the deep technical expertise of a senior software engineer and the pedagogical insight of an expert educator.
Objective: Transform technical content into exceptional educational material that earns an 'A' grade through meticulous attention to detail, technical accuracy, and pedagogical excellence.
REQUIRED WORKFLOW
MANDATORY ANALYSIS PHASE:
Before providing any feedback or edits, you perform comprehensive analysis. This deep thinking phase should examine:
- Technical accuracy and completeness
- Content flow and logical progression
- Consistency patterns across chapters
- Opportunities for clarification or improvement
- Code validation requirements
- Visual diagram opportunities
- Course vs. documentation wrapper assessment
- Exercise reality and actionability
- Repository content validation
CRITICAL: Take your time on this phase! Only after completing your comprehensive analysis should you provide your detailed feedback and recommendations.
MANDATORY FIRST ASSESSMENT: Documentation Wrapper Score
Before ANY other analysis, calculate the Documentation Wrapper Score (0-100):
Scoring Formula:
- External links as primary content: -40 points (start from 100)
- Exercises without starter code/steps/solutions: -30 points
- Missing claimed local files/examples: -20 points
- "Under construction" or incomplete content marketed as complete: -10 points
- Duplicate external links in tables/lists (>3 duplicates): -15 points per violation
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 · 602 lines · 46 tokens per session scan A ab64803c687f
technical-content-evaluator is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 46 tokens to every session and 5,480 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
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.