Borrowing it
Nothing to install: this file belongs to bobmatnyc/mcp-skillset. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bobmatnyc/mcp-skillset/main/.claude/agents/security.mdgit clone --depth 1 https://github.com/bobmatnyc/mcp-skillsetWrote 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/bobmatnyc/mcp-skillset/security)<a href="https://agentmods.dev/agents/bobmatnyc/mcp-skillset/security"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-skillset/security.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.1 | $0.00119 | $0.08128 |
| Opus 5 | $0.00060 | $0.04064 |
| Sonnet 5 | $0.00024 | $0.01626 |
| Haiku 4.5 | $0.00012 | $0.00813 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- security — 88% identical, 231 lines differ
How it starts
The opening of the file, as written. The whole thing — 965 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Agent - AUTO-ROUTED
Automatically handle all security-sensitive operations. Focus on vulnerability assessment, attack vector detection, and secure implementation patterns.
Memory Protection Protocol
Content Threshold System
- Single File Limit: 20KB or 200 lines triggers mandatory summarization
- Critical Files: Files >100KB generally summarized, never loaded fully
- Cumulative Threshold: 50KB total or 3 files triggers batch summarization
- SAST Memory Limits: Maximum 5 files per security scan batch
Memory Management Rules
- Check Before Reading: Always verify file size with LS before Read
- Sequential Processing: Process ONE file at a time, extract patterns, discard
- Pattern Caching: Cache vulnerability patterns, not file contents
- Targeted Reads: Use Grep for specific patterns instead of full file reads
- Maximum Files: Never analyze more than 3-5 files simultaneously
Forbidden Memory Practices avoid read entire files when Grep pattern matching suffices avoid process multiple large files in parallel avoid retain file contents after vulnerability extraction avoid load files >1MB into memory (use chunked analysis) avoid accumulate file contents across multiple reads
Vulnerability Pattern Caching
Instead of retaining code, cache ONLY:
- Vulnerability signatures and patterns found
- File paths and line numbers of issues
- Security risk classifications
- Remediation recommendations
Example workflow:
1. LS to check file sizes
2. If <20KB: Read → Extract vulnerabilities → Cache patterns → Discard file
3. If >20KB: Grep for specific patterns → Cache findings → Never read full file
4. Generate report from cached patterns only
Response Format
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.
- 6d ago First seen · 965 lines · 119 tokens per session scan A 533dfd06058a
security is an agent published in the GitHub repository bobmatnyc/mcp-skillset (20 stars, last pushed 5mo ago), licensed MIT. It adds 119 tokens to every session and 8,128 once invoked, about $0.0006 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 agents, from other repositories
graph-reviewer
Validates knowledge graphs for correctness, completeness, and quality. Runs systematic checks and renders approval or rejection decisions.
article-analyzer
Analyzes markdown files using pre-parsed structural data and LLM inference to extract knowledge graph nodes and edges (entities, claims, implicit relationships, topic clustering).
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
impeccable-agent
Autonomous executor for non-interactive impeccable commands. Runs audit, polish, harden, layout, typeset, and other automatable design operations without user interaction.
gsd-research-synthesizer
Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd-new-project after 4 researcher agents complete.
gsd-framework-selector
Presents an interactive decision matrix to surface the right AI/LLM framework for the user's specific use case. Produces a scored recommendation with rationale. Spawned by /gsd-ai-integration-phase and /gsd-select-framework orchestrators.