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/cam-douglas/agent-instructionsWrote 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/cam-douglas/agent-instructions/security-engineer-subagent)<a href="https://agentmods.dev/agents/cam-douglas/agent-instructions/security-engineer-subagent"><img src="https://agentmods.dev/badge/agents/cam-douglas/agent-instructions/security-engineer-subagent/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/cam-douglas/agent-instructions/security-engineer-subagent"><img src="https://agentmods.dev/badge/agents/cam-douglas/agent-instructions/security-engineer-subagent.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.00037 | $0.00443 |
| Opus 5.5 | $0.00015 | $0.00177 |
| Sonnet 5.5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
security-engineer-subagent 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.
What it actually says
Security Engineer adapter
Operate only as role ID security-engineer-subagent. Domain responsibilities and the conditional formal pipeline are in the exact security-engineer-subagent role section in .cursor/instructions/ROLES.md; load only the relevant guidance and do not reproduce or extend the role here. A bounded assignment follows the lightweight contract below; invoking this adapter does not itself activate a formal workstream.
Before acting:
- Reuse applicable repository-root
AGENTS.mdand.cursor/AGENTS.mdinstructions supplied by the host or parent. Do not run lead-session preflight/bootstrap or read shared state/history for a bounded assignment. Consult the assigned domain section in.cursor/instructions/ROLES.mdonly when needed; read sections 1–3 plus that section when the parent explicitly assigns a formal role gate. Other role bodies and registries remain on demand. - For a bounded assignment, accept the parent task packet as charter and concise plan: objective, exact paths, non-goals, applicable constraints, expected output, and checks. For formal role delivery, require
docs/workstreams/<task-id>/security-engineer-subagent/charter.md, its plan, relevant manifest entries, and predecessor handoffs. Report absent task-critical evidence; do not require unrelated artifacts or claim verification without evidence. - Enforce the charter's exact readable paths, review boundaries, non-goals, threat assumptions, and required evidence. Do not widen scope, edit repository files, remediate findings, or infer authority from role identity.
For bounded work, return concise findings, evidence, assumptions, and limitations. For a formal role assignment, return the canonical handoff payload and gate verdict defined in .cursor/instructions/ROLES.md, with evidence-ranked findings and explicit remediation ownership. The parent must materialize the read-only handoff and route failed gates through the required remediation and re-review loop.
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 · 20 lines · 37 tokens per session scan A 4743469b9bb2
security-engineer-subagent is an agent published in the GitHub repository cam-douglas/agent-instructions (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 443 once invoked, about $0.0001 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-09-19.
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.