armis-appsec-mcp copilot-instructions.md

armis-appsec-mcp copilot-instructions.md is an instructions file for GitHub Copilot from ArmisSecurity/armis-appsec-mcp. It costs 660 tokens per session, scanned A, original, Apache-2.0.

Instructions for using an application-security scanner that checks code changes for vulnerabilities before they are committed or shared.

In plain words
What is it for?
Use them to scan staged code, fix high- or critical-severity issues, rescan the fixes, and approve acknowledged findings when necessary.
Why use it?
They add a security checkpoint for staged changes and explain how to handle serious findings or mark unavoidable risks for approval.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/armissecurity/armis-appsec-mcp/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/ArmisSecurity/armis-appsec-mcp

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for armis-appsec-mcp copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/armissecurity/armis-appsec-mcp/copilot-instructions.svg)](https://agentmods.dev/instructions/armissecurity/armis-appsec-mcp/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/armissecurity/armis-appsec-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/armissecurity/armis-appsec-mcp/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 660 This file is loaded in full into every session.
When invoked 660 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00660 $0.00660
Opus 5 $0.00330 $0.00330
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

Measured 4d ago against content hash 12fec9a01f8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

armis-appsec-mcp copilot-instructions.md 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.github/copilot-instructions.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Armis AppSec Scanner — Copilot Instructions

This project uses the Armis AppSec MCP server for AI-powered security scanning.

Before Committing Code

Before running git commit, git push, or creating a pull request:

  1. Call scan_diff with staged=true and repo_path set to your repo's absolute work-tree root (the value of git rev-parse --show-toplevel, not just your current dir) to scan staged changes. Always pass repo_path: the MCP server is a long-lived process whose own working directory may be a different checkout than yours (in a git worktree it is often the main repo), so without repo_path the scan and its .scan-pass land in the wrong git dir and the commit gate never sees them.
  2. If HIGH or CRITICAL findings are reported:
    • Attempt to fix them (move secrets to env vars, use parameterized queries, etc.)
    • Re-stage fixes and re-scan
    • If findings cannot be fixed, present them to the user and ask for explicit approval
    • Only call approve_findings after the user acknowledges the risk
  3. If scan is clean (no HIGH/CRITICAL), proceed with the commit

On-Demand Scanning

When the user asks to "scan", "security check", or "check for vulnerabilities":

Scenario Tool Parameters
Staged/unstaged changes scan_diff staged=true or ref=main, plus repo_path=/absolute/repo/path
A specific file scan_file file_path=/absolute/path
Pasted code snippet scan_code code="...", optional filename
Check scanner config debug_config (none)

Suppressing False Positives

Two ways to suppress a finding the team has reviewed and accepted. Both are deterministic (no AI judgment) and apply to scan_diff, scan_file, and the git commit hook:

  1. Inline comment — add armis:ignore in a comment on the finding's line (or the line above). Narrow it with cwe:, severity:, or category: (combined with AND logic), e.g. password = os.environ["PW"] # armis:ignore cwe:798 reason: loaded from env. A bare armis:ignore suppresses any finding on that line.
  2. .armisignore file at the repo root — cwe:, severity:, category: directives and path patterns, applied repo-wide.

Read the full file on GitHub · 49 lines

Changes

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.

  1. 4d ago First seen · 49 lines · 660 tokens per session scan A 12fec9a01f8c

Subscribe to this mod's changes

armis-appsec-mcp copilot-instructions.md is an instructions file published in the GitHub repository ArmisSecurity/armis-appsec-mcp (6 stars, last pushed 23d ago), licensed Apache-2.0. It adds 660 tokens to every session, about $0.0033 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-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens