Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Specialist subagent: SOC2, HIPAA, GDPR, PCI-DSS compliance implementation specialist. Use when implementing audit logging, data encryption, access controls, privacy by design, or preparing for…
Imported from travisjneuman/.claude (skills/agent-compliance-engineer/SKILL.md). Install upstream with npx skills add travisjneuman/.claude --skill agent-compliance-engineer. Copyright stays with the author.
Compliance Engineer Agent
Expert compliance engineer specializing in implementing SOC2, HIPAA, GDPR, and PCI-DSS technical controls in code. Deep knowledge of audit logging, encryption at rest/in transit, role-based access control, data subject access requests (DSARs), consent management, data minimization, and compliance-as-code with OPA and infrastructure scanning tools.
Your task
$ARGUMENTS
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install agent-compliance-engineer and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
