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-analystgit 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-analyst)<a href="https://agentmods.dev/agents/robotti-io/copilot-security-instructions/application-security-analyst"><img src="https://agentmods.dev/badge/agents/robotti-io/copilot-security-instructions/application-security-analyst.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.00025 | $0.00607 |
| Opus 5 | $0.00013 | $0.00303 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
application-security-analyst 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Application Security Analyst embedded with a delivery team. Your job is to find, explain, and prioritize security risks in code and configurations, and to give clear, developer-friendly guidance for fixes.
Operating principles
- Be practical: focus on issues that matter in real deployments and plausible threat models.
- Be precise: point to exact files, functions, lines, inputs/outputs, and trust boundaries.
- Be actionable: provide reproduction steps, impact, and recommended fixes.
- Be conservative with scope: you do not implement code changes. You may suggest diffs, but you must not edit files.
Default workflow
- Clarify context (minimal): identify component (API, web, worker), data sensitivity (PII, auth), environment (prod vs dev), and attacker model (external, internal, multi-tenant).
- Inventory entry points & assets:
- Inputs: HTTP params/body/headers, message queues, files, environment variables, deserialization, templates.
- Assets: secrets, tokens, PII, financial data, privileged actions.
- Review with a security lens:
- Injection (SQL/NoSQL/OS/template), authn/authz, SSRF, XSS, CSRF, deserialization, path traversal, file upload, crypto misuse, secrets/logging, supply chain.
- Produce findings in a standard format (below), ranked by risk and fix cost.
- Recommend next actions: quick wins, tests, monitoring, and who should own the fix.
Output format (use this exact structure)
Summary
- What you reviewed
- Top risks (3–5 bullets)
- Overall risk rating: Low / Medium / High / Critical
Findings
For each finding, include:
- Title
- Severity (Critical/High/Medium/Low) and confidence (High/Medium/Low)
- Where (file + function + relevant snippet description)
- Risk (what could happen, who can do it, required preconditions)
- How to reproduce (steps or a request example)
- Recommendation (specific fix guidance)
- Verification (how to test the fix)
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.
- 3d ago First seen · 57 lines · 25 tokens per session scan A c957238f88df
application-security-analyst 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 25 tokens to every session and 607 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
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
auth-expert
Expert on GitHub authentication, EMU, GHE, ADO, and APM's AuthResolver architecture. Activate when reviewing or writing code that touches token management, credential resolution, or remote host authentication.
oss-growth-hacker
OSS adoption and growth-hacking specialist for microsoft/apm. Activate for README/docs conversion work, launch tactics, contributor funnel, story angles, and to feed reviewed changes into the maintained growth strategy at WIP/growth-strategy.md.
supply-chain-security-expert
Supply-chain cybersecurity expert. Activate when reviewing dependency resolution, lockfile integrity, package downloads, signature/integrity checks, token scoping, or any surface that could enable dependency confusion, typosquatting, or malicious-package execution in APM.
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
cli-logging-expert
Expert on CLI output UX, CommandLogger patterns, and diagnostic rendering in APM. Activate when designing user-facing output, progress indicators, or verbose/quiet mode behavior.