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/dfirtnt/huntable-cti-studio/python-package-safetygit clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-StudioWrote 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/dfirtnt/huntable-cti-studio/python-package-safety)<a href="https://agentmods.dev/rules/dfirtnt/huntable-cti-studio/python-package-safety"><img src="https://agentmods.dev/badge/rules/dfirtnt/huntable-cti-studio/python-package-safety.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.00382 | $0.00382 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
python-package-safety 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 3d 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
Python Package Safety (safety-mcp)
When Adding or Importing Packages
Whenever you:
- Add a package to
requirements.txt,requirements-*.txt, orpyproject.toml - Import a new Python package in code
You MUST:
- Call safety-mcp
get_recommended_version(orcheck_package_security) for the package. - Use the recommended / latest secure version returned by safety-mcp—not an arbitrary or outdated version.
- If safety-mcp reports vulnerabilities for your chosen version, upgrade to the secure version before adding it.
When User Asks to Check Existing Package
When a user asks you to check an existing package for vulnerabilities:
- Call safety-mcp
check_package_securitywith the package name and current version. - Evaluate whether there are secure versions within the same major version (e.g., 2.x → 2.y) and report these options.
- Inform the user of the latest secure version of the package (from
get_recommended_version). - For vulnerability details, use
list_vulnerabilities_affecting_versiononly when the user asks for more detail.
Tool Usage
- get_recommended_version:
packages: [{"name": "package-name", "ecosystem": "pypi"}]— returns recommended secure version. - check_package_security:
packages: [{"name": "package-name", "version": "1.2.3", "ecosystem": "pypi"}]— checks if version has vulnerabilities. - list_vulnerabilities_affecting_version: Use when user explicitly asks for vulnerability details.
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.
- 3d ago First seen · 32 lines · 382 tokens per session scan A 132d03e17586
python-package-safety is a cursor rule published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 5d ago), licensed MIT. It adds 382 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
no-jumping-ahead
ALWAYS follow these rules when working on this codebase.
cursorrules
aggregatereports to keep SUMMARY.md and metadata.json synchronized.
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-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.