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 JanoshMoshiri/MarkdownLLM --skill compliance-patterns-workflowgit clone --depth 1 https://github.com/JanoshMoshiri/MarkdownLLMWrote 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/janoshmoshiri/markdownllm/compliance-patterns-workflow)<a href="https://agentmods.dev/skills/janoshmoshiri/markdownllm/compliance-patterns-workflow"><img src="https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/compliance-patterns-workflow/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/janoshmoshiri/markdownllm/compliance-patterns-workflow"><img src="https://agentmods.dev/badge/skills/janoshmoshiri/markdownllm/compliance-patterns-workflow.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.00013 | $0.01659 |
| Opus 5 | $0.00006 | $0.00830 |
| Sonnet 5 | $0.00003 | $0.00332 |
| Haiku 4.5 | $0.00001 | $0.00166 |
Grade A, and why
Compliance Patterns Workflow 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 9d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Patterns Workflow
Primary Process: Building a Regulated Domain
When you're building a domain that operates under regulatory constraints, the Compliance Patterns library helps you encode compliance as verifiable reasoning.
Phase 1: Study Existing Patterns
Before building your domain:
- Identify your regulatory constraints — What regulations apply? (GDPR, HIPAA, SOX, etc.)
- Load relevant patterns — Study pattern things in this library
- Understand multi-lens reasoning — See how domain specification, compliance, and audit logic interact
- Identify common patterns — What decisions repeat in your domain?
Phase 2: Design Your Domain With Compliance Built-In
When defining your domain in your own domain.specification.skill.md:
- Document regulatory constraints — What rules apply?
- Define reasoning lenses — How will you approach compliance?
- Create example patterns — Add domain-specific examples to your domain
- Link to reference patterns — Reference patterns from this library where applicable
Phase 3: Create Domain-Specific Examples
In your domain's things/:
- Document patterns — Create
type: patternthings for compliant behaviors in your context - Document anti-patterns — Show violations and how to fix them
- Create decision trees — Reusable frameworks for recurring compliance decisions
- Store in git — Build your library and audit trail
Phase 4: Use Patterns During Execution
When working within your domain:
- Reference patterns — When making compliance decisions, load relevant examples
- Reason through multi-lens — Apply domain, compliance, and audit logic
- Document precedent — If you make a compliance decision, document it as a thing
- Grow your library — Over time, your domain accumulates its own pattern library
Phase 5: Audit and Review
Periodically:
- Review pattern usage — Are patterns being applied consistently?
- Update patterns — Did you discover edge cases? Update the pattern.
- Validate alignment — Do all three lenses still align?
- Share patterns — Contribute back to the reference library
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.
- 9d ago First seen · 205 lines · 13 tokens per session scan A ed86d231bafb
Compliance Patterns Workflow is a skill published in the GitHub repository JanoshMoshiri/MarkdownLLM (5 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 1,659 once invoked, about $0.0001 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-04.
Other skills, from other repositories
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…