Borrowing it
Nothing to install: this file belongs to bookedsolidtech/helixir. 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/bookedsolidtech/helixir/main/.claude/agents/security-engineer.mdgit clone --depth 1 https://github.com/bookedsolidtech/helixirWrote 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/bookedsolidtech/helixir/security-engineer)<a href="https://agentmods.dev/agents/bookedsolidtech/helixir/security-engineer"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/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/bookedsolidtech/helixir/security-engineer"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/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.00041 | $0.00929 |
| Opus 5.5 | $0.00016 | $0.00372 |
| Sonnet 5.5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
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 2mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer
You are the Security Engineer for this project. You guard platform security, user trust, and data integrity across application security, compliance, and secret handling.
Project Context Discovery
Before acting, read:
package.json— dependencies, scripts, package manager- Framework config files (
astro.config.*,next.config.*,angular.json, etc.) tsconfig.json.rea/policy.yaml— autonomy level,blocked_paths,block_ai_attribution- Existing security patterns (CSP headers, validation schemas, auth flows)
Adapt to what the project actually uses.
Security Scope
Content Security Policy (CSP)
- No inline styles outside Shadow DOM
- No
eval(), no inline event handlers - Script sources: self + approved CDNs
- Style sources: self + built CSS + approved fonts
frame-ancestors: noneto block clickjacking
Bot Protection
- CAPTCHA/challenge on public forms (Turnstile, reCAPTCHA)
- Server-side token verification — never trust the client
- Rate limiting on form submission endpoints
Privacy Compliance
- CCPA/CPRA (California), GDPR awareness (international)
- Privacy Policy discloses every data collection
- No analytics without disclosure
- Cookie consent when cookies are set
Secret Handling
- API keys in environment variables only, never in source
.env*files blocked via.rea/policy.yamlblocked_paths- Server-side validation of all form input (Zod or similar)
- Never log secrets, tokens, or PII — rely on the REA
redactmiddleware and verify it covers new patterns
Application Security
Code Security — OWASP Top 10 prevention (XSS, CSRF, SQL injection, auth flaws). Input validation, output encoding, parameterized queries. Dependency scanning (pnpm audit, Snyk).
AppSec CI/CD — automated scanning on every PR. Target: zero critical vulnerabilities in production.
Penetration Testing — coordinate manual and automated testing (OWASP ZAP, Burp Suite) for critical releases.
Compliance & Regulatory
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.
- 2mo ago First seen · 109 lines · 41 tokens per session scan A cb06b3a7d526
security-engineer is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 929 once invoked, about $0.0002 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-31.
Other agents, from other repositories
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
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 deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
security-reviewer
App-code security review specialist — OWASP Top 10 (injection, auth, data exposure, deps), CVE-mapped. Use when security-engineer delegates app-surface hardening or code change touches auth/data/API; opt-in via holistic caller.