OpenGAP is a framework-independent standard for defining AI agents as Git repositories, using files such as an agent manifest and identity document. It is intended for portable, version-controlled agents that can be adapted to systems such as Claude Code, OpenAI, LangChain, CrewAI, and AutoGen. The catalogue skills represent workflows and extensions built around this agent format.
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 open-gitagent/opengap --skill regulatory-analysisgit clone --depth 1 https://github.com/open-gitagent/opengapWrote 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/open-gitagent/opengap/regulatory-analysis)<a href="https://agentmods.dev/skills/open-gitagent/opengap/regulatory-analysis"><img src="https://agentmods.dev/badge/skills/open-gitagent/opengap/regulatory-analysis/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/open-gitagent/opengap/regulatory-analysis"><img src="https://agentmods.dev/badge/skills/open-gitagent/opengap/regulatory-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.00618 |
| Opus 5.5 | $0.00024 | $0.00247 |
| Sonnet 5.5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
regulatory-analysis 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regulatory Analysis
Instructions
When analyzing a document or process for regulatory compliance:
- Identify scope — Determine which regulatory frameworks apply (FINRA, SEC, Fed, CFPB)
- Map to rules — Identify specific rules, notices, and guidance documents relevant to the subject
- Assess compliance — Evaluate the subject against each applicable requirement
- Classify findings — Rate each finding by severity (CRITICAL, HIGH, MEDIUM, LOW, INFORMATIONAL)
- Recommend remediation — Provide specific, actionable steps to address each finding
- Assess confidence — Rate your confidence in each finding (HIGH, MEDIUM, LOW)
- Validate citations — Verify all cited rules exist and are current before finalizing
Regulatory Priority Order
When multiple frameworks apply, prioritize in this order:
- SEC rules and regulations (federal statute)
- FINRA rules (SRO requirements)
- Federal Reserve supervisory guidance
- CFPB guidance and circulars
Output Format
## Regulatory Analysis Report
### Subject: [Description]
### Date: [ISO 8601]
### Analyst: compliance-analyst v1.0.0
### Confidence: [Overall confidence level]
### Applicable Frameworks
- [List of applicable regulatory frameworks with specific rules]
### Findings
#### CRITICAL
- **[Finding Title]** — [Framework] Rule/Section [Number]
- Issue: [Description]
- Evidence: [What was observed]
- Remediation: [Specific steps]
- Confidence: [HIGH/MEDIUM/LOW]
#### HIGH
[Same format]
#### MEDIUM
[Same format]
#### LOW
[Same format]
### Summary
[1-2 paragraph summary of overall compliance posture]
### Disclaimer
This analysis is for informational purposes only and does not constitute legal advice.
Example Finding
#### CRITICAL
- **Inadequate Suitability Disclosure** — FINRA Rule 2111
- Issue: Customer account agreement lacks suitability questionnaire for complex products
- Evidence: Section 4.2 references "suitable investments" without defining suitability criteria or risk tolerance assessment
- Remediation: Add suitability assessment form per FINRA Rule 2111.05 (Supplementary Material) before account opening
- Confidence: HIGH
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 · 81 lines · 59 tokens per session scan A cf9014ad928d
regulatory-analysis is a skill published in the GitHub repository open-gitagent/opengap (2,981 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 618 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 skills, from other repositories
travel-expense-audit
A travel-expense review workflow that checks reimbursement claims against policy handbooks and rate tables. It covers items such as hotel, transport, and daily meal allowances.
procurement-audit
A procurement review workflow that checks contracts and purchase documents against uploaded purchasing rules. It links each finding to the relevant rule and supporting text.
polymarket
Query Polymarket: markets, prices, orderbooks, history.
risk-scoring
Score how concentrated and risky a portfolio is on a 0-100 scale from its position weights. Use when the user asks how risky their portfolio is, whether it is too concentrated, or for a diversification check.
valuation
Estimate whether a stock looks cheap or expensive using a price-to-earnings (P/E) based fair-value method. Use when the user asks if a stock is over- or under-valued, or for a fair-value / target price.
cost-efficiency-analyzer
Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…