agentleFS
Sign inStart free
ZenRowsZenRows/cli/skills/compliance-policy/SKILL.md

compliance-policy

Skill16 starsChanged 27 days agoMITView on GitHub

Respect domain allow/deny rules, credit limits, and secret handling.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. OBaruch/ai-native-sdlc-template★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every cloud call is checked against .zenrows/policy.json before it runs.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compliance & policy

Every cloud call is checked against .zenrows/policy.json before it runs.

Policy knobs

zenrows policy show
zenrows policy set max_credits_per_run 5000
zenrows policy set blocked_domains "example.com,foo.test"
zenrows policy set allowed_domains "mysite.com"      # non-empty = allow-list mode
zenrows policy set allow_browser false               # opt OUT of browser (on by default)
zenrows policy set allow_experimental true

Hard rules

  • Never print or commit API keys. Keys live in .zenrows/secrets.json (0600, gitignored) and are redacted from logs and run artifacts.
  • Respect allowed_domains / blocked_domains — enforced by the CLI (→ POLICY_BLOCKED_DOMAIN).
  • max_credits_per_run / max_pages_per_run / max_concurrency are advisory budgets surfaced by zenrows status (not hard-enforced by the CLI today) — self-limit against them.
  • Confirm destructive uninstall with --yes.
  • Experimental commands are off by default (allow_experimental). Browser is on by default (opt out with allow_browser=false).

See [[cost-control]] and [[trace-debug]].

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free