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 VectorPeak/vectorpeak-agent-skills --skill job-contract-review-vpgit clone --depth 1 https://github.com/VectorPeak/vectorpeak-agent-skillsWrote 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/vectorpeak/vectorpeak-agent-skills/job-contract-review-vp)<a href="https://agentmods.dev/skills/vectorpeak/vectorpeak-agent-skills/job-contract-review-vp"><img src="https://agentmods.dev/badge/skills/vectorpeak/vectorpeak-agent-skills/job-contract-review-vp/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/vectorpeak/vectorpeak-agent-skills/job-contract-review-vp"><img src="https://agentmods.dev/badge/skills/vectorpeak/vectorpeak-agent-skills/job-contract-review-vp.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.00088 | $0.01185 |
| Opus 5.5 | $0.00035 | $0.00474 |
| Sonnet 5.5 | $0.00018 | $0.00237 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
job-contract-review-vp 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 2mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Contract Review
Purpose
Review job-related contracts from the likely signing party's perspective. Convert files to text, identify contract type, force structured analysis, validate the structure, and render a practical Markdown report.
Default to Chinese for summaries, explanations, suggestions, missing protections, negotiation points, disclaimers, and final Markdown reports. Preserve exact contract quotes in the original contract language.
This skill follows a fixed review workflow: extract document text, analyze against a strict schema, validate the JSON, then render a report.
Workflow
- If the user provides a file, extract text with
scripts/extract_contract_text.py. - If the user pasted contract text, save it to a temporary
.txtonly when a script needs a file input. - Read
references/review_prompt.mdand use it as the analysis contract. - Read
references/contract_type_checks.mdfor contract-type-specific risks and missing-protection checks. - Have Codex perform the contract analysis directly from the extracted text and produce JSON only, matching
schemas/contract_review.schema.json. Use Chinese for generated content except exact quotes and schema enum values. - Validate the JSON with
scripts/validate_contract_review.py. - If validation fails, ask the LLM to repair the JSON only; do not change the source contract text.
- Render the final Markdown report using
scripts/render_contract_report.py, or render directly from the validated JSON when needed. - Include a concise legal disclaimer: this is AI-assisted review, not legal advice.
Analysis Responsibility
Codex performs the risk analysis. Do not require the user to configure OpenAI, OpenRouter, Claude, Kimi, Ollama, or any other external model provider just to use this skill.
The bundled scripts handle deterministic work:
- file text extraction
- JSON validation
- Markdown rendering
Codex handles judgment work:
- identifying red flags
- distinguishing warnings from severe risks
- recognizing protective clauses
- spotting missing protections
- assigning fairness score and grade
- writing negotiation suggestions
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 126 lines · 88 tokens per session scan A e59118103551
job-contract-review-vp is a skill published in the GitHub repository VectorPeak/vectorpeak-agent-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 1,185 once invoked, about $0.0004 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-31.
Other skills, from other repositories
policy-lookup
Find and explain company policies in plain language. Trigger with "what's our PTO policy", "can I work remotely from another country", "how do expenses work", or any plain-language question about benefits, travel, leave, or handbook rules.
crisis-holding
Draft crisis holding statements, journalist Q&A posture, and what-not-to-say guidance from confirmed incident facts, with a hard legal-counsel gate. Builds each statement through proven crisis-comms frameworks (holding-statement anatomy, SCCT, CAP order, the legitimate non-answer, bridge/flag/block).
ai-ethics-review
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety…
ai-usage-policy
Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog. Use when asked for a company AI policy, acceptable-use rules for ChatGPT/Claude/Copilot at work, guidance on what data may go into AI tools, or to fix a policy…
planning-application-statement
Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will receive. Use when asked to write a design and access statement, planning statement, or supporting statement for a planning…
kyc-escalation
Write an internal KYC/AML escalation memo: a factual time-stamped trigger description, customer-profile vs activity mismatch analysis, red-flag taxonomy mapping, outstanding information, and a recommendation with rationale. Use when asked to escalate a KYC alert, document an AML concern, write up unusual-activity…