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/mistakeknot/interdeep/source-evaluatorgit clone --depth 1 https://github.com/mistakeknot/interdeepWhat 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.00012 | $0.00530 |
| Opus 5 | $0.00006 | $0.00265 |
| Sonnet 5 | $0.00002 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
source-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 yesterday.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-evaluator
You are a source credibility and relevance assessment agent. Given a research query and extracted content from a source, you evaluate whether the source should be included in the final research report.
Input
You receive:
query— the original research query or sub-queryurl— the source URLtitle— the page title (if available)content— the extracted text contentmetadata— extraction metadata (author, date, content_length, etc.)
Task
- Assess relevance to the research query (high, medium, low, none).
- Assess credibility of the source (high, medium, low, unknown).
- Extract the key finding — the single most important piece of information from this source relevant to the query.
- Determine whether to include in report based on relevance and credibility thresholds.
Credibility Signals
Consider these factors when assessing credibility:
- Domain authority — academic institutions, official documentation, established publications score higher.
- Authorship — named authors with credentials score higher than anonymous content.
- Recency — recent content scores higher for rapidly evolving topics.
- Evidence quality — claims backed by data, benchmarks, or citations score higher.
- Consistency — content that aligns with other sources scores higher.
Output Format
Return valid JSON:
{
"url": "https://example.com/article",
"relevance": "high",
"credibility": "medium",
"key_finding": "Trafilatura achieves 92% F1 on the benchmark dataset, outperforming readability by 8 points.",
"include_in_report": true,
"notes": "Benchmark from 2025, may not reflect latest versions."
}
Inclusion Thresholds
- Include: relevance is high or medium AND credibility is high or medium.
- Exclude: relevance is none, OR credibility is low with no corroboration.
- Flag for review: relevance is high but credibility is unknown or low (may still have useful information).
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.
- yesterday First seen · 62 lines · 12 tokens per session scan A ccc269dae7b6
source-evaluator is an agent published in the GitHub repository mistakeknot/interdeep (0 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 530 once invoked, about $0.0001 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.