document-review

A review process for financial documents such as prospectuses, investment-adviser documents, and marketing materials. It checks whether they follow rules from FINRA, the US financial-industry regulator, and SEC disclosure requirements.

In plain words
What is it for?
Checking documents for required disclaimers, risk-and-benefit balance, document classification, disclosure prominence, and required approval status. Findings include the issue, location, rule reference, and recommended fix.
Why use it?
It helps find missing disclosures, misleading claims, unbalanced descriptions of risks and benefits, and incorrectly formatted warnings before publication.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/open-gitagent/opengap/document-review
Any agent
npx skills add open-gitagent/opengap --skill document-review
Clone the repo
git clone --depth 1 https://github.com/open-gitagent/opengap

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 460 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00059 $0.00460
Opus 5 $0.00030 $0.00230
Sonnet 5 $0.00012 $0.00092
Haiku 4.5 $0.00006 $0.00046

Measured 2d ago against content hash dac29534a66d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

document-review 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 2d 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.

examples/full/skills/document-review/SKILL.md · 52 lines

What it actually says

Document Review

Instructions

When reviewing a financial document:

  1. Classify the document — Determine document type (prospectus, ADV, customer agreement, marketing material, etc.)
  2. Identify applicable rules — Map to FINRA 2210 (communications), SEC disclosure requirements, etc.
  3. Check required elements — Verify all required disclosures, disclaimers, and content are present
  4. Assess accuracy — Flag potentially misleading, exaggerated, or promissory statements
  5. Check balance — Per FINRA 2210, ensure risks and benefits are presented in a balanced manner
  6. Review formatting — Verify required prominence of disclosures

Key Checks

  • All required disclosures present
  • No misleading or exaggerated claims
  • Balanced presentation of risks and benefits
  • Proper disclaimers included
  • Correct classification (correspondence/retail/institutional)
  • Principal pre-approval status verified (if retail communication)

Output Format

For each finding, produce:

### [SEVERITY] — [Rule Reference]
- **Issue**: [What was found]
- **Location**: [Section/page reference]
- **Recommended action**: [Specific fix]

Example Finding

### WARNING — FINRA 2210(d)(1)(A)
- **Issue**: Performance claim "consistently outperforms the market" lacks supporting data and time period
- **Location**: Page 2, paragraph 3
- **Recommended action**: Add specific time period, benchmark comparison, and standardized performance data per SEC Rule 482
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. 2d ago First seen · 52 lines · 59 tokens per session scan A dac29534a66d

Subscribe to this mod's changes

document-review is a skill published in the GitHub repository open-gitagent/opengap (2,921 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 460 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

a0-create-agent

Create a new Agent Zero agent profile (subordinate). Covers where profiles live (user / plugin-distributed / project-scoped), the agent.yaml schema, the prompt inheritance & override model, and optional profile-specific tools and extensions. Use for any "create/add/new agent profile" request.

agent0ai/agent-zero · 63 tokens

skill-packager

Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs packageskill to produce a standards-compliant zip, and uses installskill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a…

vixues/LeAgent · 87 tokens

document-processor

Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.

vixues/LeAgent · 44 tokens

workflow-helper

Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.

vixues/LeAgent · 41 tokens

attendance-signin-sheet

Generate printable attendance / 签到表 spreadsheets from name lists. Use when the user asks for 签到表, attendance sheet, meeting sign-in table, or similar printable roster tables (not full payroll attendance scoring unless asked).

vixues/LeAgent · 51 tokens

data-analyzer

Guidance for analyzing structured data, generating statistics and producing data-driven insights. Use when the user asks to analyze data, compute statistics, find patterns, or generate analytical reports.

vixues/LeAgent · 39 tokens