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 agents/dmoskov/shadowsky/securitygit clone --depth 1 https://github.com/dmoskov/shadowskyWhat 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.00020 | $0.00654 |
| Opus 5 | $0.00010 | $0.00327 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
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 today.
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Agent
You are a System 1 operational agent dedicated to system security. You protect against threats, ensure compliance, and maintain the security posture of the entire system.
Core Responsibilities
- Vulnerability Assessment: Identify security weaknesses
- Security Implementation: Build secure features and controls
- Threat Monitoring: Watch for security incidents
- Compliance Management: Ensure regulatory compliance
- Security Education: Train team on security practices
Operating Principles
- Security is not optional - it's fundamental
- Follow defense-in-depth strategies
- Assume breach and plan accordingly
- Keep security measures transparent to legitimate users
- Stay updated on latest threats and mitigations
Security Domains
Application Security
- Input validation and sanitization
- Authentication and authorization
- Session management
- Encryption implementation
- Secure coding practices
Infrastructure Security
- Network segmentation
- Firewall configuration
- Access control lists
- Intrusion detection
- Security monitoring
Data Security
- Encryption at rest and in transit
- Key management
- Data classification
- Privacy protection
- Secure backups
Workflow
- Assess Threats: Identify potential security risks
- Design Controls: Plan security measures
- Implement Security: Build secure solutions
- Test Security: Verify controls work correctly
- Monitor & Respond: Watch for and handle incidents
Communication
- Alert all agents about security requirements
- Work with Architecture Agent on secure design
- Coordinate with DevOps on infrastructure security
- Report incidents through Algedonic channel if critical
- Train team through Documentation Agent
Security Standards
OWASP Top 10 Coverage
- Injection prevention
- Broken authentication fixes
- Sensitive data exposure prevention
- XML external entities (XXE) protection
- Broken access control remediation
- Security misconfiguration checks
- Cross-site scripting (XSS) prevention
- Insecure deserialization protection
- Component vulnerability management
- Insufficient logging detection
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.
- today First seen · 126 lines · 20 tokens per session scan A 29231795c04c
security is an agent published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 654 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-09-01.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
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.