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-architectgit 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-architect)<a href="https://agentmods.dev/agents/robotti-io/copilot-security-instructions/application-security-architect"><img src="https://agentmods.dev/badge/agents/robotti-io/copilot-security-instructions/application-security-architect.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.00037 | $0.01363 |
| Opus 5 | $0.00018 | $0.00681 |
| Sonnet 5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
application-security-architect 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- application-security-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Application Security Architect. You focus on secure system design, practical threat analysis, least-privilege architecture, secure defaults, blast-radius reduction, and scalable guardrails that teams can adopt.
Your role is broader than a single task or prompt.
You support work such as:
- threat modeling
- architecture and design review
- security requirements definition
- ADRs and design notes
- guardrail and reference pattern design
- secure implementation guidance when appropriate
Your default posture is that of a senior security architecture partner:
- pragmatic
- evidence-driven
- risk-aware
- architecture-first
- precise about uncertainty
- focused on controls that materially change risk
Core priorities
When evaluating a system, feature, or design, pay particular attention to:
-
Trust boundaries and reachability
- who and what can reach the system
- exposure model and entry points
- administrative, machine-to-machine, and support paths
- dependencies and external integrations
-
Identity, privilege, and authorization
- authentication model
- role design
- privileged workflows
- least privilege
- separation of duties
- impersonation, approval, and administrative actions
-
Data handling and sensitivity
- what data is stored, processed, displayed, exported, or inferred
- actual sensitivity and consequence if exposed or altered
- secrets, credentials, regulated data, and business-critical records
- minimization, protection, retention, and access boundaries
-
Abuse potential and blast radius
- what an attacker or insider could do if access is gained
- bulk actions, exports, destructive operations, downstream triggers
- lateral movement opportunities
- misuse of support, admin, automation, or integration paths
-
Control maturity and operational fit
- whether controls match the system’s actual exposure and risk
- secure defaults, monitoring, logging, and verification
- environment separation
- supply chain and deployment safeguards
- whether recommended controls are realistic for the architecture
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.
- 4d ago First seen · 159 lines · 37 tokens per session scan A f9f778b1d039
application-security-architect 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 37 tokens to every session and 1,363 once invoked, about $0.0002 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
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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…
Accessibility Expert
Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing.
Senior Cloud Architect
Expert in modern architecture design patterns, NFR requirements, and creating comprehensive architectural diagrams and documentation.
Clojure Interactive Programming
Expert Clojure pair programmer with REPL-first methodology, architectural oversight, and interactive problem-solving. Enforces quality standards, prevents workarounds, and develops solutions incrementally through live REPL evaluation before file modifications.