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 skills add alexclowe/awesome-copilot-cowork-plugins --skill evidence-relevance-checkergit clone --depth 1 https://github.com/alexclowe/awesome-copilot-cowork-pluginsWrote 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/skills/alexclowe/awesome-copilot-cowork-plugins/evidence-relevance-checker)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/evidence-relevance-checker"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/evidence-relevance-checker/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/skills/alexclowe/awesome-copilot-cowork-plugins/evidence-relevance-checker"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/evidence-relevance-checker.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.00026 | $0.00636 |
| Opus 5 | $0.00013 | $0.00318 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
evidence-relevance-checker 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 13d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in the Federal Rules of Evidence and common admissibility issues in litigation. When the user is working on litigation-related tasks, apply this knowledge automatically.
Core competencies
Relevance and prejudice (FRE 401-403):
- Apply the low bar of FRE 401 relevance, then weigh FRE 403 prejudice/confusion
- Flag FRE 404(b) other-acts evidence — admissible only for a non-propensity purpose (motive, opportunity, intent, plan, knowledge, identity, absence of mistake)
- Apply FRE 407 (subsequent remedial measures), 408 (settlement), 409 (medical expenses), 410 (plea negotiations), 411 (insurance) exclusions
Hearsay (FRE 801-807):
- Identify out-of-court statements offered for truth (hearsay) vs. non-hearsay uses (effect on listener, verbal acts, prior inconsistent statements under 801(d)(1))
- Apply party-opponent admissions (FRE 801(d)(2)) — including agency, co-conspirator, and adoptive admissions
- Walk through 803 exceptions (present sense impression, excited utterance, then-existing condition, business records, public records, etc.) and 804 unavailability exceptions
- Flag double-hearsay (FRE 805) — every layer needs an exception
Authentication and chain of custody (FRE 901-902):
- Identify methods of authentication: witness familiarity, distinctive characteristics, voice ID, electronic signatures, hash values for digital evidence
- Flag self-authenticating documents (FRE 902 — public records, certified business records under 902(11)/(12))
- Apply chain-of-custody requirements for physical evidence and digital forensics
Character, expert, and privilege issues:
- FRE 404-405 character evidence rules (criminal vs. civil, methods of proof)
- FRE 702 expert qualification, reliability (Daubert factors), and FRE 703 basis-of-opinion rules
- Privilege (attorney-client, work product, spousal, doctor-patient, clergy) — note no general federal privilege for accountants
Communication style
When assisting with admissibility tasks:
- For each evidence item, output: rule(s) implicated, ruling (admissible / inadmissible / conditionally admissible), reasoning, foundation needed.
- Suggest the foundation questions or stipulations needed to admit borderline evidence.
- Flag judge-specific tendencies if the user names the bench (otherwise note that rulings vary by chambers).
- Always note that outputs are drafts requiring attorney verification before use.
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.
- 13d ago First seen · 44 lines · 26 tokens per session scan A a6e5858ca4fe
evidence-relevance-checker is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 636 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-30.
Other skills, from other repositories
works-council-reviewer
Reviews a proposal, business case, deck or rollout plan in character as a Works Council Representative archetype, then saves a structured review document with a verdict, findings that cite the artifact, employee-impact risks and five interrogation questions. Use when the user asks for a works council review, an…
general-counsel-reviewer
Reviews a proposal, business case, deck or plan in character as a General Counsel archetype, then saves a structured review document with a verdict, findings that cite the artifact, legal risks and five interrogation questions. Use when the user asks for a legal review, a general counsel pressure-test of a document…
personal-data-protection
Personal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP 27/2022, Thailand PDPA B.E. 2562 (2019), Malaysia PDPA 2010 (with the 2024 Amendments), or Philippines DPA (RA 10173). Use when reviewing or modifying code that touches personal data …
eu-ai-act-readiness
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency, high-risk controls, general-purpose AI obligations, governance, and implementation milestones. Use when an organization…
compliance-checklist-generation
Build evidence-oriented readiness checklists for frameworks such as SOC 2, HIPAA, PCI DSS, and GDPR, with gaps and remediation priorities. Use when the user needs an internal readiness assessment or control-mapping plan; do not use it to certify compliance or replace an auditor or counsel.
license-analysis
Analyze open-source license compatibility, obligations, and compliance risks across project dependencies. Use when the user requests license analysis or provides relevant inputs for this workflow.