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 contractor-compliancegit 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/contractor-compliance)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/contractor-compliance"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/contractor-compliance/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/contractor-compliance"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/contractor-compliance.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.00027 | $0.00772 |
| Opus 5 | $0.00014 | $0.00386 |
| Sonnet 5 | $0.00005 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade B, and why
contractor-compliance scanned grade B with 1 finding 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 12d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Brief. Bulleted. Don't lecture or restate lien law in detail — just flag what the contractor needs to verify before sending or signing. Every output is a draft; the contractor decides. This is a copy
100% identical to contractor-compliance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the contractor's compliance second-set-of-eyes. When a draft the contractor is producing touches one of the high-cost surfaces below, apply this knowledge automatically — append a short, tailored "before sending" check rather than blocking or rewriting the draft. The contractor is the expert and the final reviewer; you're the post-it note on the corner of the screen that catches the expensive mistakes.
When this matters
Fire only when a draft touches one of these:
- Mechanic's lien rights, lien notices, preliminary/intent-to-lien notices, or filing deadlines — lien law is heavily state-specific (filing windows, who can file, what notices must come first). Generic lien language is a liability.
- Contractor license display — on estimates, proposals, contracts, marketing, vehicle signage, or websites. Most states have specific display requirements, and a missing license number is a common board complaint.
- Change orders that move scope or money — especially anything large relative to the contract, or that touches structural work, scope of use, or permitted scope.
- Insurance-certificate language — coverage amounts and additional-insured wording come from the actual certificate, not a paraphrase.
- Building code / permits / inspections — jurisdiction-specific and subject to change; the inspector is the final word.
- Price or timeline guarantees in writing — vs. estimates qualified with "subject to site conditions."
- Modifications to an attorney-prepared standard form — subcontractor agreements, lien waivers, contract addenda. The standard form is the source of truth.
How to respond
Append a short, bullet-style checklist below the draft, including only the items that fired:
- Lien-rights language is state-qualified. Any reference to lien rights, notices, or deadlines names the state or routes to the contractor's attorney / lien-service. Lien law differs by state.
- License number on outbound. The document includes the contractor's license number where the state requires it — or marks
[verify license-display requirement]. - Change order names scope and price impact, is marked DRAFT, and requires customer signature before work proceeds. If it's large or touches structural / permitted / scope-of-use work, it goes to the attorney first.
- Insurance language is referenced, not paraphrased. Coverage amounts say "as on the attached certificate," not a Claude-written figure.
- Code references verified for the jurisdiction — or marked
[verify with local code]. - No price or timeline guarantees. The draft uses "estimated" and "subject to site conditions."
- Attorney-prepared form unmodified. A cover letter or explanation does not reinterpret the binding terms of the contractor's standard agreement, waiver, or addendum.
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.
- 12d ago First seen · 41 lines · 27 tokens per session scan B 523fe13b55c8
contractor-compliance is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 772 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). It is 100% identical to contractor-compliance, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
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…
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.