read-a-contract

read-a-contract is a skill for Claude Code, Codex from akiotanaka847/qaio-desktop. It costs 81 tokens per session (1,291 once invoked), scanned A, original, MIT.

A contract-reading tool that finds important terms and shows the exact wording alongside a plain-language explanation. It covers items such as liability limits, ending the contract, automatic renewal, payment, intellectual property, data handling, uptime promises, and exclusivity.

In plain words
What is it for?
Use it to extract specific clauses, compare renewal or liability terms across vendor contracts, or review a scanned PDF after its text has been read.
Why use it?
It reduces the need to search through legal language by hand and highlights terms that may need attention. It can examine one contract or a group of contracts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to extract specific clauses, compare renewal or liability terms across vendor contracts, or review a scanned PDF after its text has been read.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akiotanaka847/qaio-desktop/read-a-contract
Install

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.

Any agent
npx skills add akiotanaka847/qaio-desktop --skill read-a-contract
Clone the repo
git clone --depth 1 https://github.com/akiotanaka847/qaio-desktop

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for read-a-contract

README.md
[![agentmods](https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/read-a-contract/github.svg)](https://agentmods.dev/skills/akiotanaka847/qaio-desktop/read-a-contract)
Your own site
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/read-a-contract"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/read-a-contract/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.

agentmods 80×15 button for read-a-contract

Your own site · 80×15
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/read-a-contract"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/read-a-contract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,291 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.01291
Opus 5 $0.00041 $0.00646
Sonnet 5 $0.00016 $0.00258
Haiku 4.5 $0.00008 $0.00129

Measured 5d ago against content hash abc72cc97d30, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

read-a-contract 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 5d 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.

store/agents/operations/.agents/skills/read-a-contract/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Read A Contract

When to use

  • "pull the {clause} from this contract" (single doc).
  • "what are the auto-renew terms in every contract in this folder" (batch).
  • "extract the liability cap and termination language from {vendor}'s master service agreement".

Connections I need

I run external work through Composio. Before this skill runs I check the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.

  • Files (Google Drive) - Required for batch runs and named-vendor lookups. I scan folders or named contracts here.
  • Document processing (OCR or PDF text extraction) - Required. Pulls the actual text out of scanned or native PDFs so I can extract clauses verbatim.

If no files provider is connected and you haven't pasted the contract, I stop and ask you to connect Google Drive or paste the document.

Information I need

I read your operations context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.

  • The contract itself - Required. Why I need it: I can't extract from nothing. If missing I ask: "Drop the contract or point me at the folder. PDF, Word, or a Google Doc all work."
  • Vendor posture - Required. Why I need it: tells me which terms count as a flag. A conservative posture flags more aggressively than fast-risk. If missing I ask: "How do you approach vendor terms - conservative, balanced, or move fast?"
  • Operating context doc - Required. Why I need it: anchors hard nos so I flag clauses that would violate them. If missing I ask: "Want me to set up your operating context first? Helps me catch unfavorable terms more reliably."

Steps

  1. Read context/operations-context.md. If missing: stop, ask user run set-up-my-ops-info skill first. Vendor posture + hard nos anchor "unfavorable terms" flags.

  2. Read config/procurement.json - approval posture decide which terms count as "flag worthy" (conservative founder flag more; fast-risk founder flag only truly egregious).

Read the full file on GitHub · 83 lines

Changes

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.

  1. 5d ago First seen · 83 lines · 81 tokens per session scan A abc72cc97d30

Subscribe to this mod's changes

read-a-contract is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 6d ago), licensed MIT. It adds 81 tokens to every session and 1,291 once invoked, about $0.0004 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-09-05.