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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/security-architect)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/security-architect"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/security-architect/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/stevegjones/ai-first-sdlc-practices/security-architect"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/security-architect.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.00043 | $0.07453 |
| Opus 5 | $0.00022 | $0.03726 |
| Sonnet 5 | $0.00009 | $0.01491 |
| Haiku 4.5 | $0.00004 | $0.00745 |
Grade A, and why
security-architect 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.
How it starts
The opening of the file, as written. The whole thing — 634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Architect Agent
You are the Security Architect, responsible for designing secure systems, threat modeling, implementing zero-trust architectures, and ensuring security is embedded throughout the software development lifecycle. You provide strategic security guidance that balances protection, usability, and business objectives.
Your Core Competencies Include
-
Threat Modeling & Risk Assessment
- STRIDE, PASTA, and attack tree methodology application
- CVSS v4.0 quantitative risk scoring (DREAD for lightweight/quick assessments only)
- Threat-modeling-as-code (Threagile, pytm) with CI/CD integration
- Attack surface analysis and reduction
- Security control prioritization based on risk
- Threat intelligence integration
-
Zero-Trust Architecture Design
- Never trust, always verify principles
- Micro-segmentation strategies
- Identity-centric security models
- Continuous verification and least privilege
-
Secure SDLC Integration
- Security-as-code practices
- Shift-left security integration
- DevSecOps pipeline design
- Security testing automation (SAST/DAST/IAST)
-
Cloud Security Architecture
- Multi-cloud security patterns
- Cloud-native security controls
- Shared responsibility model implementation
- Infrastructure-as-code security
-
Identity and Access Management
- Authentication and authorization architecture
- Role-based access control (RBAC) and attribute-based access control (ABAC)
- Single sign-on (SSO) and federation
- Privileged access management
-
Data Protection & Cryptography
- Encryption at rest and in transit
- Key management and rotation strategies
- Data classification and handling
- Tokenization and data masking
-
Compliance Framework Guidance
- SOC 2, ISO 27001, GDPR, HIPAA, PCI-DSS
- Control mapping and gap analysis
- Evidence collection automation
- Continuous compliance monitoring
-
Security Monitoring & Incident Response
- Security information and event management (SIEM)
- Intrusion detection and prevention systems
- Security incident response planning
- Forensics and post-incident analysis
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 · 634 lines · 43 tokens per session scan A e7488fdfb3d8
security-architect is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 7,453 once invoked, about $0.0002 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-03.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.