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/davidl71/project-management-automationWrote 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/davidl71/project-management-automation/semgrep)<a href="https://agentmods.dev/rules/davidl71/project-management-automation/semgrep"><img src="https://agentmods.dev/badge/rules/davidl71/project-management-automation/semgrep/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/davidl71/project-management-automation/semgrep"><img src="https://agentmods.dev/badge/rules/davidl71/project-management-automation/semgrep.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.00707 | $0.00707 |
| Opus 5.5 | $0.00283 | $0.00283 |
| Sonnet 5.5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
semgrep 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semgrep MCP Server Usage
When to Use Semgrep
ALWAYS use Semgrep for:
- Security vulnerability scanning
- Code quality checks
- Pattern-based code analysis
- Security best practices enforcement
- Before committing code changes
Usage Pattern: Use Semgrep when:
- Scanning code for security issues
- Checking for common vulnerabilities
- Enforcing coding standards
- Reviewing code before deployment
- Validating security practices
Examples
✅ Good:
- "Scan this code with Semgrep for security vulnerabilities"
- "Check this code with Semgrep for common issues"
- "Use Semgrep to validate this security implementation"
- "Run Semgrep on this file before committing"
❌ Avoid:
- General code questions (use Cursor AI or Context7)
- Documentation lookups (use Context7)
- Code generation (use Cursor AI)
Benefits
- Security: Detects common vulnerabilities and security issues
- Quality: Enforces coding standards and best practices
- Automation: Can be integrated into CI/CD pipelines
- Comprehensive: Scans for hundreds of security patterns
Integration with Other Tools
- With Ollama: Semgrep for security scanning, Ollama for code analysis
- With Context7: Semgrep for security, Context7 for library documentation
- Before commits: Always run Semgrep before committing security-sensitive code
Workflow for Security Review
- Before changes: Run Semgrep on modified files
- Review findings: Address security issues found
- Fix issues: Implement fixes for identified vulnerabilities
- Re-scan: Verify fixes resolved the issues
Best Practices
Security Scanning
- Scan before commit: Always scan code before committing
- Fix critical issues: Address high-severity findings immediately
- Review all findings: Don't ignore warnings without review
- Regular scans: Run scans periodically on the entire codebase
Query Optimization
- Be specific: "Scan this file for SQL injection vulnerabilities"
- Provide context: Include file paths or code sections
- Review output: Always review Semgrep findings carefully
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.
- 1mo ago First seen · 118 lines · 707 tokens per session scan A 62dac38b1bbd
semgrep is a cursor rule published in the GitHub repository davidl71/project-management-automation (1 stars, last pushed 8mo ago), licensed MIT. It adds 707 tokens to every session, about $0.0028 per session on Opus 5.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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.