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.
npx agentmods add rules/trustlists/trustlists-plugin/trustlists-vendor-reviewgit clone --depth 1 https://github.com/trustlists/trustlists-pluginWrote 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/trustlists/trustlists-plugin/trustlists-vendor-review)<a href="https://agentmods.dev/rules/trustlists/trustlists-plugin/trustlists-vendor-review"><img src="https://agentmods.dev/badge/rules/trustlists/trustlists-plugin/trustlists-vendor-review.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00459 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade B, and why
trustlists-vendor-review scanned grade B with 1 finding 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 4d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Don't lecture; one short note about supply chain visibility is enough What it actually says
trustlists vendor review guidance
When editing a dependency manifest (package.json, requirements.txt, go.mod, etc.), the user may be adding a new third-party vendor to their supply chain.
Before recommending a new dependency
- Search the package or vendor name with
trustlists_search, then usetrustlists_lookupwith the identified domain to check its exact public trustlists record - If they do, mention the listed frameworks (SOC 2, ISO 27001, HIPAA documentation, PCI DSS) as directory labels, not as proof
- If they don't, say the vendor is not in the current public directory and suggest checking the vendor's own security page before committing
When the user asks to "audit" or "review" their dependencies
- Use the
trustlists_audit_dependenciesMCP tool against the workspace root - Follow the
audit-dependenciesskill for structuring the report
Compliance-sensitive contexts
If you can tell from the codebase the user works in a regulated industry, weight the analysis accordingly:
- Healthcare (
hipaa,phi,ehr,medicalin code/comments) → note whether the record lists HIPAA information, then tell the user to confirm BAA and scope - Payments (
stripe,pci,card,paymentintegrations) → note whether the record lists PCI DSS - EU customers (
gdpr,dpo, EU data residency code) → treat GDPR as a listed privacy signal, not a certification - Government / FedRAMP (
.govdeploys,fedramp) → note whether the record lists FedRAMP
Don't
- Don't block the user from adding a dependency just because it lacks a trust center; many open-source libraries are pure code with no SaaS backend
- Don't fabricate frameworks. Only report what the directory record lists
- Don't lecture; one short note about supply chain visibility is enough
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.
- 4d ago First seen · 36 lines · 0 tokens per session scan B a4daa439d62d
trustlists-vendor-review is a cursor rule published in the GitHub repository trustlists/trustlists-plugin (0 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 459 tokens. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.