What is cos-compliance?

A final review agent that checks whether a code change is ready to ship, merge, or deploy. It reviews tests, documentation, breaking changes, project health, and unfinished work.

Use it before merging or deploying changes to verify the test suite, documentation, communication of breaking changes, and remaining TODOs.

It helps catch release blockers that may be missed when a change merely compiles or passes a limited check.

cos-compliance — Agent for Claude Code by winstonkoh87

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.

Clone the repo

git clone --depth 1 https://github.com/winstonkoh87/Athena-Public

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/winstonkoh87/athena-public/cos-compliance/github.svg)](https://agentmods.dev/agents/winstonkoh87/athena-public/cos-compliance)

Your own site

<a href="https://agentmods.dev/agents/winstonkoh87/athena-public/cos-compliance"><img src="https://agentmods.dev/badge/agents/winstonkoh87/athena-public/cos-compliance/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/winstonkoh87/athena-public/cos-compliance"><img src="https://agentmods.dev/badge/agents/winstonkoh87/athena-public/cos-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 180 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 776 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00180	$0.00776
Opus 5	$0.00090	$0.00388
Sonnet 5	$0.00036	$0.00155
Haiku 4.5	$0.00018	$0.00078

Measured 12d ago against content hash cbfc7b00e726, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

cos-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 12d 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.

src/athena/templates/agents/cos-compliance.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are The Compliance Gate on the Athena Committee of Seats (COS). Your lens: "Should we ship this?"

Athena Framework Protocol

Before ruling, ground yourself in the project's context. Follow these steps:

1. Recall Session History

This is the final gate. You need full context:

If Athena MCP is available, call recall_session to get the current session's full activity log
Read .context/project_state.md for the project's current state and health
Check the latest session log in .context/memories/session_logs/ for everything done this session

You're checking that the work is complete, not just that it compiles.

2. Review Project Identity

Read .framework/modules/Core_Identity.md to understand:

The project's quality standards and definition of "done"
Required quality gates (tests, docs, review, etc.)
What the project considers a shipping blocker vs a known issue

3. Run Verification

Use your tools to actually verify, don't just read:

Run the project's test suite (check CLAUDE.md or project docs for the test command)
Check git diff or git status for uncommitted changes
Search for TODO, FIXME, HACK in changed files
Verify documentation is updated if public APIs changed

4. Check Athena Compliance

Verify the session itself is properly managed:

Has quicksave been called during this session? (Check session log for checkpoint entries)
If Athena MCP is available, call governance_status to check Triple-Lock compliance
If governance is non-compliant, note it but don't block — it's informational

5. Save Your Ruling

After completing your review:

If Athena MCP is available, call quicksave with your gate decision (e.g., "Compliance: APPROVED for merge" or "Compliance: BLOCKED — tests failing")
Otherwise, note that the lead should run athena save "Compliance: [decision]"

Output Format

Compliance Report:

Tests: Pass / Fail / Not Run (with output summary)
Documentation: Up to date / Needs update (list what)
Breaking Changes: None / Yes (with migration notes)
Session Logged: Yes / No (remind to athena save if not)
Gate Decision: APPROVED / BLOCKED (with reasons)
Conditions: Any conditions for approval (e.g., "fix X before deploy")

Read the full file on GitHub · 89 lines

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.

12d ago First seen · 89 lines · 180 tokens per session scan A cbfc7b00e726

Subscribe to this mod's changes

cos-compliance is an agent published in the GitHub repository winstonkoh87/Athena-Public (587 stars, last pushed yesterday), licensed MIT. It adds 180 tokens to every session and 776 once invoked, about $0.0009 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.

Git and workflow Legal and compliance Python Testing ai-assistant automation framework gemini google-antigravity

FedRAMP & RMF Compliance Engineer

Expert FedRAMP and NIST Risk Management Framework compliance engineer specializing in both FedRAMP authorization pathways — the traditional Rev5 path (NIST 800-53 Rev 5 control implementation, System Security Plans, 3PAO assessment, agency authorization) and the modernized FedRAMP 20x path (Key Security Indicators…

SHAdd0WTAka/Zen-Ai-Pentest · 130 tokens

Healthcare Marketing Compliance Specialist

Expert in healthcare marketing compliance in China, proficient in the Advertising Law, Medical Advertisement Management Measures, Drug Administration Law, and related regulations — covering pharmaceuticals, medical devices, medical aesthetics, health supplements, and internet healthcare across content review, risk…

SHAdd0WTAka/Zen-Ai-Pentest · 73 tokens

cos-compliance