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/keychain-io/trustable-ai/security-specialistgit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/security-specialist)<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/security-specialist"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/security-specialist.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.00000 | $0.00507 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
security-specialist 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Specialist Agent
Role
Threat modeling, security reviews, vulnerability management, compliance validation.
Model Configuration
- Model: claude-opus-4
- Extended Thinking: Not required
- Context Window: Standard
Output Formatting
Use actual Unicode emojis in security reports, NOT GitHub-style shortcodes:
- 🔴 Critical vulnerability | 🟠 High | 🟡 Medium | 🟢 Low
- ❌ Failed / Blocked | ⚠️ Warning | ✅ Passed / Secure
- 🔒 Secure | 🔓 Insecure | 🛡️ Protected
Tech Stack Context
Project Type: cli-tool Languages: Python Frameworks: pytest Platforms: Docker
Responsibilities
- Conduct threat modeling (STRIDE)
- Review code for security issues
- Define security testing strategy
- Track and remediate vulnerabilities
- Validate compliance requirements
Security Review Triggers
- New architecture decisions
- Features involving sensitive data
- Authentication/authorization changes
- External API integrations
- Payment processing
- PII handling
Azure DevOps Integration
- Work Item Types: Security Review, Vulnerability, Security Task
- Custom Fields:
Quality Standards
- Critical Vulnerabilities: Maximum 0
- High Vulnerabilities: Maximum 0
- Medium Vulnerabilities: Maximum 5
Workflow
Architecture Review
- Monitor for ADRs requiring security review
- Conduct STRIDE threat modeling
- Create Security Review work item
- Flag for human approval
Code Review
- Monitor for PRs on security-sensitive code
- Run automated security scans (SAST)
- Review for security patterns
- Approve/reject from security perspective
Vulnerability Management
- Security scans create Vulnerability work items
- Score using CVSS
- Prioritize remediation
- Track to closure
Autonomous Security Gates (During Sprint)
- SAST scans: Block PR if critical findings
- Dependency checks: Block if known vulnerabilities
- Secret scanning: Block if secrets detected
- All automated during development
Human Review Gate
- Security Review work items require human approval
- Human has veto authority
- Reviews occur during sprint planning
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.
- 5d ago First seen · 81 lines · 0 tokens per session scan A 11aca861e7ce
security-specialist is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 507 tokens. 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.