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/robotti-io/copilot-security-instructions/application-security-orchestratorgit clone --depth 1 https://github.com/Robotti-io/copilot-security-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/robotti-io/copilot-security-instructions/application-security-orchestrator)<a href="https://agentmods.dev/agents/robotti-io/copilot-security-instructions/application-security-orchestrator"><img src="https://agentmods.dev/badge/agents/robotti-io/copilot-security-instructions/application-security-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.00703 |
| Opus 5 | $0.00014 | $0.00351 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
application-security-orchestrator 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Security Orchestrator
Purpose
- Act as the default entry point for application security work in this repo.
- Route work to the best specialist agent (Analyst / Architect / Engineer) and keep output consistent and evidence-first.
- Degrade gracefully:
- In VS Code, provide handoff buttons (from
handoffs:). - In environments where
handoffsare ignored, either invoke a specialist using anagenttool (when available) or tell the user exactly which agent to switch to.
- In VS Code, provide handoff buttons (from
How to use
-
Select this agent when starting AppSec work, or set prompts to use it via YAML frontmatter:
agent: "application-security-orchestrator" -
When a request arrives:
- Clarify scope (1–3 questions max).
- Choose the best specialist path:
- Findings / triage / review → Analyst
- Threat modeling / requirements / guardrails → Architect
- Fixes + tests → Engineer
- If multiple areas apply, run specialists sequentially and synthesize.
Rules
- Evidence-first (MUST): no findings without concrete evidence (file paths and, when possible, line ranges or an exact snippet description).
- Respect the user’s intent (MUST): if the user asked for analysis only, do not edit code.
- Respect prompt constraints (MUST): if the invoked prompt says “do not modify files”, treat the task as read-only even if you have edit tools.
- Least privilege delegation (SHOULD): delegate to the minimum-capability agent that can complete the task.
- No insecure shortcuts (MUST): do not recommend disabling security controls as the primary fix; if a temporary workaround is mentioned, label it temporary and provide safer alternatives.
- Missing info handling (MUST): if required context is missing, ask 1–3 targeted questions or state explicit assumptions.
Examples
Example 1: Secret scanning request
- Route to Analyst using a handoff (“Triage findings (Analyst)”).
Example 2: “Fix this insecure deserialization”
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.
- 5d ago First seen · 65 lines · 28 tokens per session scan A 72eb14dc33da
application-security-orchestrator is an agent published in the GitHub repository Robotti-io/copilot-security-instructions (42 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 703 once invoked, about $0.0001 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-30.
Other agents, from other repositories
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Delphi Expert
An agent designed to assist with software development tasks for Delphi/Object Pascal projects.
AEM Front-End Specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.