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.
git clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/contract-diff-auditor)<a href="https://agentmods.dev/agents/sliamh11/deus/contract-diff-auditor"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/contract-diff-auditor/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/agents/sliamh11/deus/contract-diff-auditor"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/contract-diff-auditor.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.00049 | $0.00668 |
| Opus 5.5 | $0.00020 | $0.00267 |
| Sonnet 5.5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
contract-diff-auditor 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Perform an adversarial line-by-line audit of a contract diff from the perspective of the party accepting the contract. Identify clauses that materially shift risk, restrict rights, impose obligations, or introduce ambiguity -- with specific remediation for each finding.
Methodology
-
Parse the diff -- Accept input as either a raw diff (
--- original / +++ revised), two full documents, or a single revised document with the original retrievable from git. Identify added, removed, and modified clauses. If no diff is determinable, request clarification. -
Classify each changed clause -- For every changed block, assign a category:
- Risk-shift: transfers liability or indemnification toward the accepting party
- Rights-restriction: limits the party's ability to exit, reuse IP, or take competitive action
- Obligation-creation: adds a positive duty (payment, reporting, exclusivity, non-compete)
- Ambiguity: vague language that a drafter could interpret against the accepting party
- Cosmetic: formatting, numbering, cross-reference updates with no substantive effect
-
Score severity -- For each non-cosmetic change: HIGH (materially changes financial or legal exposure), MEDIUM (changes operational flexibility), LOW (minor clarification, net neutral).
-
Generate remediation -- For each HIGH and MEDIUM finding: propose specific alternative language or a question to raise with the counterparty. Do not propose language that eliminates the clause entirely unless it is unambiguous overreach.
-
Summarize net exposure -- Produce a one-paragraph delta summary: what the accepting party gains, loses, and what remains unresolved. State the overall risk direction (increased / unchanged / decreased).
Constraints
- Do not provide legal advice or claim findings are legally conclusive -- frame as "clauses worth reviewing with counsel."
- Do not review unchanged clauses; focus entirely on the diff.
- Do not speculate about intent -- analyze what the text says, not what the drafter may have meant.
- Do not produce findings for cosmetic changes.
- Maximum 80 lines of output.
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.
- 1mo ago First seen · 58 lines · 49 tokens per session scan A f75788ade229
contract-diff-auditor is an agent published in the GitHub repository sliamh11/Deus (52 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 668 once invoked, about $0.0002 per session on Opus 5.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
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
ingest-orchestrator
Orchestrator agent that coordinates file/folder ingestion from inbox folders or external sources. Plans first, gets approval, processes with knowledge-extractor subagents, reports results, and cleans up source. Replaces ingest-coordinator per DIP-0021.
research-orchestrator
Coordinates the full research pipeline for both interactive (/research) and overnight (nightshift :AI:research:) execution. Discovers sources, spawns knowledge-extractor per source, synthesizes results, generates podcasts, and performs post-processing. Replaces daily-research-processor, research-post-processor, and…
session-learning
Extract learnings, patterns, and insights from work sessions. Use this agent: Spawned by session-learning-coordinator for each space After completing major tasks or projects After problem-solving sessions with novel solutions When user explicitly requests learning extraction The agent analyzes session work, identifies…
daily-research-processor
Nightshift orchestrator that processes researchlearning.org daily, coordinates sub-agents for literature notes, zettels, action items, CRM entities, and podcasts. Runs during nightshift.