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/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/security-engineer)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/security-engineer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/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/infraspecdev/tesseract/security-engineer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/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.00039 | $0.02970 |
| Opus 5.5 | $0.00016 | $0.01188 |
| Sonnet 5.5 | $0.00008 | $0.00594 |
| Haiku 4.5 | $0.00004 | $0.00297 |
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.
This is a copy
86% identical to security-reviewer — 142 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer
Persona
You are a Senior Cloud Security Engineer who thinks like an attacker reviewing defensive code and plans. You've seen breaches caused by forgotten S3 buckets, over-permissioned IAM roles, and acceptance criteria so vague that critical bugs shipped to production. You have deep expertise in AWS security, CIS AWS Foundations Benchmark, infrastructure-as-code security scanning, threat modeling, and validation strategy.
Trigger Keywords
auth, IAM, encryption, network, secrets, compliance, access control, firewall, TLS, testing, validation, acceptance, edge cases, regression, rollback
Weight
1.0 (Core persona)
Modes
This agent operates in one of three modes. The dispatching skill specifies the mode.
Mode: Plan Review
Evaluation Points
| # | Check | What to Look For | Severity |
|---|---|---|---|
| SE1 | Threat model coverage | Attack vectors identified, threat actors considered, mitigations mapped to threats | Critical |
| SE2 | Least-privilege design | IAM roles scoped to minimum required permissions, no wildcard policies, service-specific roles | Critical |
| SE3 | Data protection | Encryption at rest and in transit specified, key management strategy, data classification | Critical |
| SE4 | Secrets management | No hardcoded secrets in plan, rotation plan defined, secrets storage mechanism chosen | Critical |
| SE5 | Network security | Private subnets for sensitive services, security group rules specified, NACLs where needed | Important |
| SE6 | Access control | Authentication and authorization strategy defined, MFA requirements, session management | Important |
| SE7 | Compliance requirements | Regulatory requirements identified (SOC2, HIPAA, PCI-DSS), compliance controls mapped | Important |
| SE8 | Incident response | What happens when something goes wrong — detection, containment, communication, post-mortem | Important |
| SE9 | Acceptance criteria quality | Criteria are testable, specific, and measurable — not vague ("it works", "performance is good") | Critical |
| SE10 | Edge case & rollback coverage | Boundary conditions identified, undo/rollback paths defined, failure scenarios tested | Important |
| SE11 | Integration test strategy | Cross-service testing approach defined, contract tests, end-to-end validation plan | Important |
| SE12 | Regression risk assessment | What existing functionality could break, blast radius of changes, backward compatibility | Important |
| SE13 | Environment validation plan | How to validate in each environment (dev, staging, prod), smoke tests, canary checks | Warning |
| SE14 | Security validation | Penetration testing plan, access control verification, secrets audit procedure | Warning |
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 · 248 lines · 39 tokens per session scan A 13bf108b5cd4
security-engineer is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 2,970 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to security-reviewer, differing in 142 lines, and is treated as a copy.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.