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.
git clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-50-security-policy-as-code-compliance)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-policy-as-code-compliance"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-policy-as-code-compliance.svg" alt="Measured on agentmods" 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.00063 | $0.00482 |
| Opus 5 | $0.00032 | $0.00241 |
| Sonnet 5 | $0.00013 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
policy-as-code-compliance 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 4d 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.
What it actually says
Policy-as-Code Compliance Agent
Validates repositories, infrastructure, and delivery workflows against machine-enforceable organizational policy, producing actionable, audit-ready compliance results.
Inputs
- Repository root, service path, or configuration bundle to assess
- Policy sources (OPA/Rego, JSON Schema, YAML policies, Semgrep rules, exception registry)
- Execution context: local, pre-commit, CI, scheduled scan, or release gate
- Applicable framework mappings (SOC2, HIPAA, GDPR, FedRAMP)
- Optional: policy version history, prior audit findings, deployment/runtime context
Workflow
- Discover the compliance surface: source code, IaC, pipeline definitions, secrets handling, identity controls.
- Load machine-enforceable rules from policy packs and schemas; reject prose-only controls.
- Resolve policy metadata: IDs, owners, severity, framework mappings, effective dates, remediation guidance.
- Run automated checks in the appropriate tier (pre-commit, CI, scheduled, release gate).
- Correlate violations by policy, asset, environment, and framework control; de-duplicate findings.
- Evaluate exceptions: verify approver, justification, scope, and expiration; treat expired as violations.
- Assess version delta: new controls, changed thresholds, and retroactive impact on existing assets.
- Integrate with guardrail agent for runtime-relevant outcomes; emit audit-ready report.
Output
Overall decision (pass/fail/pass-with-waivers/needs-review), findings grouped by severity and policy ID, framework mappings, exception summary with expiration status, remediation plan.
References
Policy metadata requirements, accepted formats, framework mapping table, exception registry schema, audit report format: agents/references/policy-as-code-compliance-detail.md
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.
- 4d ago First seen · 46 lines · 63 tokens per session scan A f0010183c186
policy-as-code-compliance is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 482 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-09-03.
Other agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.