DevInder1DevInder1/supply-chain-scanner-public/.cursor/rules/tridentchain.mdc

supply-chain-scanner-public / rules

Cursor rule0 starsChanged 6 months agoMITView on GitHub

TridentChain Security — supply-chain vulnerability scanning for this workspace

We split this tridentchain.mdc into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
When the user asks to scan dependencies, check supply-chain risk, or validate fixes after upgrades:
line 9
Very specific:
If tridentchain MCP is enabled in .cursor/mcp.json, use:
line 13
Very specific:
Read .tridentchain-out/scan-report.json and HTML reports for details.
line 33
Very specific:
No API keys required for the default full profile.
line 37
Very specific:
Use --run-profile quick for faster iteration.
line 38
Distinctive:
Do not paste secrets into chat.
line 39

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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

tridentchain.mdc

---
description: TridentChain Security — supply-chain vulnerability scanning for this workspace
globs:
alwaysApply: false
---

# TridentChain Security

When the user asks to scan dependencies, check supply-chain risk, or validate fixes after upgrades:

## Preferred: MCP (if configured)

If `tridentchain` MCP is enabled in `.cursor/mcp.json`, use:

- `scan_project` — fast project-only scan
- `scan_full` — project + system + IDE extensions
- `validate_after_patch` — compare baseline vs post-patch scan JSON

Install once:

```bash
pip3 install "tridentchain-security>=0.1.1" tridentchain-mcp
```

Copy [.cursor/mcp.json.example](../mcp.json.example) to `.cursor/mcp.json` and reload MCP.

## Fallback: CLI (always works)

```bash
tridentchain-security --scan all --project-path <workspace_root> --output-dir .tridentchain-out
```

Read `.tridentchain-out/scan-report.json` and HTML reports for details.

## Notes

- No API keys required for the default `full` profile.
- Use `--run-profile quick` for faster iteration.
- Do not paste secrets into chat; use environment variables for optional NVD/GitHub keys.

See [docs/CURSOR_SETUP.md](../../docs/CURSOR_SETUP.md) and [docs/AI_INTEGRATION.md](../../docs/AI_INTEGRATION.md).

Download now (ZIP)

Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

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