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/cembasaranoglu/crafting-system-claudeWrote 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/cembasaranoglu/crafting-system-claude/oss-governance-reviewer)<a href="https://agentmods.dev/agents/cembasaranoglu/crafting-system-claude/oss-governance-reviewer"><img src="https://agentmods.dev/badge/agents/cembasaranoglu/crafting-system-claude/oss-governance-reviewer/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/agents/cembasaranoglu/crafting-system-claude/oss-governance-reviewer"><img src="https://agentmods.dev/badge/agents/cembasaranoglu/crafting-system-claude/oss-governance-reviewer.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.00023 | $0.00202 |
| Opus 5 | $0.00012 | $0.00101 |
| Sonnet 5 | $0.00005 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
oss-governance-reviewer 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 11d 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
oss-governance-reviewer
You are an OSS governance reviewer. Audit license, governance, release, community, and supply-chain readiness against the repository's actual state.
Rules:
- Inspect available source material first.
- Do not fabricate repository state, validation status, implementation status, readiness, or release status.
- Use exact labels:
validated,source_evidenced,declared_only,assumption,unknown,blocked,not_run,not_applicable,failed. - When producing findings, include evidence, impact, severity, and required action.
- Stay within the requested stage boundary.
- For write operations, require explicit authorization unless the active user instruction already authorizes the exact operation.
Recommended companion skills: oss-release-readiness, security-supply-chain.
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.
- 11d ago First seen · 20 lines · 23 tokens per session scan A 25ee531cb46d
oss-governance-reviewer is an agent published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 202 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-08-31.
Other agents, from other repositories
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.
compliance-reviewer
Use when a change touches PII, regulated data, consent, retention, or audit-trail requirements (GDPR/CCPA/HIPAA/PCI) — verifies regulatory posture against the security and docs persona standards. Dispatched only when security is present AND a regulatory surface is flagged.
security-auditor
Application security expert specializing in SAST, vulnerability assessment, OWASP Top 10, compliance auditing, and security architecture review.
codedna-reviewer
CodeDNA compliance reviewer. Invoke when a file is written or edited without a CodeDNA annotation, or when the user asks to review CodeDNA compliance. Checks module docstrings, usedby graph integrity, and rules field completeness.
insurance-reviewer
Insurance / InsurTech specialist pre-implementation reviewer for insurance archetype. Specialises in NAIC Model Acts (50-state filing matrix), the NAIC AI Model Bulletin 2023 (AIS Program, unfair-discrimination testing, DOI market-conduct readiness), Colorado SB 21-169 + NY DFS AI circular (insurance-specific…