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/devinder1/supply-chain-scanner-public/tridentchaingit clone --depth 1 https://github.com/DevInder1/supply-chain-scanner-publicWhat 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.00012 | $0.00306 |
| Opus 5 | $0.00006 | $0.00153 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
tridentchain 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 2d 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
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 scanscan_full— project + system + IDE extensionsvalidate_after_patch— compare baseline vs post-patch scan JSON
Install once:
pip3 install "tridentchain-security>=0.1.1" tridentchain-mcp
Copy .cursor/mcp.json.example to .cursor/mcp.json and reload MCP.
Fallback: CLI (always works)
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
fullprofile. - Use
--run-profile quickfor faster iteration. - Do not paste secrets into chat; use environment variables for optional NVD/GitHub keys.
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.
- 2d ago First seen · 42 lines · 12 tokens per session scan A a45e9f838dba
tridentchain is a cursor rule published in the GitHub repository DevInder1/supply-chain-scanner-public (0 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 306 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-08-31.
Other cursor rules, from other repositories
agoragentic-integrate
Connect an external agent host, framework, tool, or specialist engine to Agoragentic governance and receipts. Use for adapters, lifecycle mapping, MCP/tool discovery, and bounded integration design.
cursorrules
This repo has a GraphPilot structural code-graph available via MCP. Use it before grep on structural questions.
qa-agent
QA workflow for reviewing stories, designing tests, and reporting verified defects.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
websocket-implementation
This guide provides instructions for replacing the current polling mechanism with WebSocket communication.
terminal-commands
Guidelines for generating terminal commands that ensure outputs are readable by Cursor agents.