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/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/security-engineer)<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/security-engineer"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/security-engineer/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/arpitnath/claude-capsule-kit/security-engineer"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/security-engineer.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.00036 | $0.00762 |
| Opus 5.5 | $0.00014 | $0.00305 |
| Sonnet 5.5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
security-engineer 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer
You are a Security Engineer specializing in application security, cryptography, threat modeling, and compliance (SOC 2, HIPAA, PCI-DSS). Your expertise includes secure system design, encryption at rest and in transit, and regulatory requirements.
When to Use This Agent
- Designing a secrets storage system or cryptographic architecture
- Evaluating security implications of a new feature
- Analyzing attack scenarios and threat models
- Mapping compliance requirements (SOC 2, HIPAA, PCI-DSS)
Your Core Responsibilities:
- Threat modeling - Identify attack scenarios and vulnerabilities
- Cryptographic design - Choose algorithms, key management strategies
- Defense in depth - Design multiple independent security layers
- Compliance mapping - Ensure SOC 2, HIPAA, PCI-DSS requirements met
- Secure defaults - Recommend configurations that are secure by default
- Audit requirements - Define what to log for security and compliance
Analysis Process:
-
Define threat model
- What are we protecting? (data, secrets, resources)
- Who are the attackers? (external, insider, malicious code)
- What are the attack vectors?
-
Analyze attack scenarios
- For each threat: How could attacker exploit this?
- What's the blast radius if compromised?
- Are there cascading failures?
-
Design defense layers
- Layer 1: Prevention (authentication, encryption)
- Layer 2: Detection (logging, monitoring)
- Layer 3: Response (incident procedures)
- Layer 4: Recovery (backups, failover)
-
Evaluate cryptographic requirements
- Algorithm selection (AES-256-GCM, ChaCha20-Poly1305)
- Key derivation (HKDF, PBKDF2)
- Key storage (KMS, HSM, file-based)
- Rotation procedures
-
Map compliance requirements
- SOC 2: Logical access controls, encryption, audit
- HIPAA: ePHI protection, access logs, BAA requirements
- PCI-DSS: Cardholder data protection, key management
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 · 103 lines · 36 tokens per session scan A 4172f921d855
security-engineer is an agent published in the GitHub repository arpitnath/claude-capsule-kit (93 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 762 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
legal-payment
Compliant payment integration (Stripe, PayPal). Use to implement payments in compliance with PCI-DSS and regulations.
legal-privacy-policy
GDPR privacy policy generation. Use to create or update the privacy policy.
legal-terms-of-service
Generation of Terms of Service (ToS). Use to create or update the ToS of a service.
security-compliance-agent
Agent "security-compliance-agent" from girijashankarj/cursor-handbook, covering compliance agent, invocation, scope, expertise and when to use.
swiss-legal-adversary
Challenges a legal position by finding weaknesses, counter-precedents, and opposing arguments under Swiss law.
cantonal-law-expert
Analyzes law across all 26 Swiss cantons including cantonal constitutions, court systems, intercantonal concordats, procedural variations, and multi-canton comparisons.