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/yonatangross/orchestkitWrote 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/rules/yonatangross/orchestkit/license-compliance)<a href="https://agentmods.dev/rules/yonatangross/orchestkit/license-compliance"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/license-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.
<a href="https://agentmods.dev/rules/yonatangross/orchestkit/license-compliance"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/license-compliance.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.00017 | $0.00264 |
| Opus 5 | $0.00009 | $0.00132 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
license-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 3d 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
License Compliance
When installing new dependencies, check their license before adding to production projects.
Problematic Licenses
Avoid packages with these licenses unless explicitly approved:
- GPL-2.0 / GPL-3.0 — Copyleft, may require open-sourcing your code
- AGPL-3.0 — Network copyleft, triggers on server-side use
- LGPL-2.1 / LGPL-3.0 — Lesser copyleft, still has linking requirements
- CC-BY-NC — Non-commercial only
- SSPL — Server Side Public License, restrictive for SaaS
Before Adding Dependencies
- Check the license:
npm view <package> license - Prefer permissive licenses: MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC
- For Python:
pip show <package>to check license metadata - When in doubt, flag the dependency for review before committing
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.
- 3d ago First seen · 27 lines · 17 tokens per session scan A 7e73e4d3a24a
license-compliance is a cursor rule published in the GitHub repository yonatangross/orchestkit (264 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 264 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-09.
Other cursor rules, from other repositories
pn-tool-risk-policy
MCP tool risk tiers, HITL gates, and when to use approvalcheckpoint and gatelogappend. Use for safety reviews and workflow audits.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.