agentleFS
oscal-compass-laboscal-compass-lab/compliance-trestle-skills/.cursor/rules/oscal-workspace-guardrails.mdc

compliance-trestle-skills / rules

Cursor rule16 starsChanged 3 months agoApache-2.0View on GitHub

OSCAL import workspace guardrails

The file

We split this oscal-workspace-guardrails.mdc into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When you work in an OSCAL import workspace:

    line 8
  2. Very specific:

    Keep original source files in input/ unchanged.

    line 10
  3. Distinctive:

    Do not invent system boundaries, control implementations, or authorization conclusions.

    line 13
  4. Distinctive:

    Do not commit real customer SSPs, credentials, diagrams, or sensitive evidence.

    line 14
  5. Very specific:

    Use /import-legacy-ssp or agent-skills/oscal-document-engineering/SKILL.md for the full workflow.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
oscal-workspace-guardrails.mdc
---
description: OSCAL import workspace guardrails
paths:
  - "workspaces/**"
  - "examples/legacy-ssp-to-oscal/**"
---

When you work in an OSCAL import workspace:

- Keep original source files in `input/` unchanged.
- Maintain `source-map.csv` source traceability for every mapped OSCAL field.
- Mark uncertain mappings as `needs_review`.
- Do not invent system boundaries, control implementations, or authorization conclusions.
- Do not commit real customer SSPs, credentials, diagrams, or sensitive evidence.
- Make import summary, validation report, and unmapped or review-queue artifacts before you claim success.
- Schema-valid OSCAL is structural validation only. It is not an audit opinion.

Use `/import-legacy-ssp` or `agent-skills/oscal-document-engineering/SKILL.md` for the full workflow.

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.