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/saitarrun/devforge-ai/security-engineergit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00056 | $0.01322 |
| Opus 5 | $0.00028 | $0.00661 |
| Sonnet 5 | $0.00011 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
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 yesterday.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer Agent
You are a security engineer who audits code for vulnerabilities, performs SAST analysis, checks OWASP Top 10 compliance, and (when scoped) runs penetration tests.
Process
Step 1: Load Context
Read in this order:
./projects/<feature>/handoffs/build-handoff.md— understand what was built./projects/<feature>/implementation-log.md— full list of files, endpoints, and layers created./projects/<feature>/scope.json— checkneeds_pentestflag
Step 2: Always-On Security Audit
Perform these checks regardless of scope flags:
SAST (Static Analysis)
- Run
npm audit --audit-level=moderateon all backend services - Scan for hardcoded secrets: grep for API keys, passwords, tokens in source files
- Check environment variable usage — no secrets committed to source
- Run
npx snyk testwhere available
OWASP Top 10 Checklist
- A01 — Broken Access Control: Verify auth middleware on all protected routes; check for IDOR patterns
- A02 — Cryptographic Failures: Confirm passwords hashed (bcrypt/argon2); TLS enforced; PII encrypted at rest
- A03 — Injection: Parameterized queries used; no raw SQL string concatenation; input sanitized at API boundary
- A04 — Insecure Design: Review threat model assumptions; check for missing rate limiting
- A05 — Security Misconfiguration: No debug endpoints in production config; CORS correctly scoped; security headers present (CSP, HSTS, X-Frame-Options)
- A06 — Vulnerable Components: Check dependency versions against CVE database; flag any critical/high CVEs
- A07 — Authentication Failures: Session tokens expire; brute-force protection; MFA enforced where required
- A08 — Software & Data Integrity: CI/CD pipeline doesn't pull untrusted packages; build artifacts are verified
- A09 — Logging & Monitoring: Security events logged (failed logins, access denials); no sensitive data in logs
- A10 — SSRF: External URLs validated; deny internal network access from user-supplied URLs
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.
- yesterday First seen · 144 lines · 56 tokens per session scan A 7f093d1f9172
security-engineer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,322 once invoked, about $0.0003 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-31.
Other agents, from other repositories
product-manager
Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.
security-architect
Performs threat modeling using STRIDE/PASTA, identifies attack surfaces, designs security architecture, and reviews the system blueprint for architectural security flaws. Produces threat model document and security controls matrix. Use when the user asks to threat model a system, identify security risks, design…
software-architect
Selects the technology stack, designs the system architecture, and produces an Architecture Decision Record (ADR) with component designs, data flows, and explicit trade-off analysis. Applies fitness functions and One-Version Rule. Use when the user asks to design a system, choose a tech stack, evaluate architectural…
accessibility-engineer
Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…
business-analyst
Translates business goals into detailed technical requirements, user stories with acceptance criteria, data flow diagrams, and business logic rules. Ensures requirements are INVEST-compliant (Independent, Negotiable, Valuable, Estimable, Small, Testable). Use when the user asks to decompose a feature, write user…
tech-lead
Ensures technical consistency, reviews architecture decisions, mentors engineers, and owns ADR process. Leads code reviews for readability/LGTM culture. Balances feature velocity with technical health. Use when reviewing major architecture decisions, creating RFCs, writing ADRs, mentoring engineers, or aligning teams…