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.
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketingWrote 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/thatrebeccarae/claude-marketing/dep-audit)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/dep-audit"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/dep-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/dep-audit"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/dep-audit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.04258 |
| Opus 5 | $0.00022 | $0.02129 |
| Sonnet 5 | $0.00009 | $0.00852 |
| Haiku 4.5 | $0.00004 | $0.00426 |
Grade A, and why
dep-audit 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Cross-repository dependency audit. Scans package manifests (package.json, pyproject.toml, Cargo.toml, go.mod) for outdated packages, security advisories, version conflicts between repos, and license compatibility issues. Produces a prioritized update plan.
When to Use
- Monthly hygiene: Run on a cadence to catch dependency drift before it compounds
- Before releases: Verify no known vulnerabilities ship to production
- Security incidents: When a CVE drops, quickly assess exposure across all repos
- Onboarding new repos: Baseline the dependency health of a repo you're inheriting or adopting
Usage
/dep-audit [repo-path]— audit a single repository/dep-audit [repo-path1] [repo-path2] ...— cross-repo audit (enables version conflict detection)
Procedure
1. Detect Package Managers
Scan the target repo(s) for manifest files:
| Manager | Manifest | Lock File |
|---|---|---|
| npm | package.json |
package-lock.json |
| yarn | package.json |
yarn.lock |
| pnpm | package.json |
pnpm-lock.yaml |
| pip | requirements.txt, setup.py, setup.cfg |
requirements.txt (pinned) |
| poetry | pyproject.toml (has [tool.poetry]) |
poetry.lock |
| uv | pyproject.toml (has [tool.uv]) |
uv.lock |
| cargo | Cargo.toml |
Cargo.lock |
| go mod | go.mod |
go.sum |
# Detect which manifests exist
ls package.json pyproject.toml Cargo.toml go.mod requirements.txt 2>/dev/null
# Detect lock files
ls package-lock.json yarn.lock pnpm-lock.yaml poetry.lock uv.lock Cargo.lock go.sum 2>/dev/null
If multiple ecosystems are present (e.g., a monorepo with Node.js frontend and Go backend), audit each independently and merge results.
2. Parse Manifests and Lock Files
Read the manifest to identify declared dependencies (direct) and the lock file for resolved versions (transitive). Distinguish between:
- Production dependencies (
dependencies,[dependencies], main requires) - Development dependencies (
devDependencies,[dev-dependencies], extras)
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.
- 9d ago First seen · 392 lines · 44 tokens per session scan A 33cda311ef95
dep-audit is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (133 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 4,258 once invoked, about $0.0002 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
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.