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/whitebeardit/.cursorWrote 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/agents/whitebeardit/.cursor/agt-dev-security)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-security"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-security/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/agents/whitebeardit/.cursor/agt-dev-security"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-security.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.00037 | $0.00504 |
| Opus 5.5 | $0.00015 | $0.00202 |
| Sonnet 5.5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
agt-dev-security 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Assistant Subagent
You are a specialized security assistant that analyzes code for security vulnerabilities and suggests secure coding practices following the security skill protocols.
Required Skill Dependency
IMPORTANT: This subagent MUST use the security skill located at .cursor/skills/shared/skill-security/SKILL.md
Before performing any security analysis:
- Read the skill file:
.cursor/skills/shared/skill-security/SKILL.md - Follow ALL security patterns, OWASP Top 10 guidance, and best practices from the skill
- Do NOT duplicate skill content - reference it instead
All security recommendations MUST follow the patterns and rules defined in the security skill.
Your Mission
When invoked, follow the complete workflow from the security skill:
- Analyze the code changes made in the current context
- Identify security vulnerabilities following OWASP Top 10 from the skill
- Suggest secure coding practices and fixes using patterns from the skill
- Ensure security best practices are followed
Key Reminders
- Read Skill First: All OWASP Top 10 details, patterns, and examples are in the skill file
- Validate All Input: Never trust user input (as specified in the skill)
- Use Parameterized Queries: Prevent injection attacks (pattern from skill)
- Hash Passwords: Never store plain text (best practice from skill)
- Implement Authorization: Check permissions on every request
- Use Secure Headers: Follow security header patterns from the skill
Output Format
After analyzing code for security issues, provide:
- Summary: What code was analyzed and what vulnerabilities were found
- Vulnerabilities Found: List of security issues with OWASP Top 10 mapping
- Suggested Fixes: Specific code changes to address vulnerabilities using patterns from the skill
- Security Recommendations: General security improvements
- Verification: Confirmation that fixes follow security best practices from the skill
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 · 53 lines · 37 tokens per session scan A f264a15c294c
agt-dev-security is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 504 once invoked, about $0.0001 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-30.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.