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 skills/armissecurity/armis-appsec-mcp/security-scannpx skills add ArmisSecurity/armis-appsec-mcp --skill security-scangit clone --depth 1 https://github.com/ArmisSecurity/armis-appsec-mcpWrote 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/skills/armissecurity/armis-appsec-mcp/security-scan)<a href="https://agentmods.dev/skills/armissecurity/armis-appsec-mcp/security-scan"><img src="https://agentmods.dev/badge/skills/armissecurity/armis-appsec-mcp/security-scan.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.1 | $0.00110 | $0.02752 |
| Opus 5 | $0.00055 | $0.01376 |
| Sonnet 5 | $0.00022 | $0.00550 |
| Haiku 4.5 | $0.00011 | $0.00275 |
Grade A, and why
security-scan 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 6d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/security-scan
On-demand security scanning powered by AI SAST. Scans code snippets, files, or git diffs for vulnerabilities and reports findings with CWE IDs, severity, line numbers, and fix suggestions.
Usage
/security-scan-- scan staged changes (falls back to unstaged if nothing staged)/security-scan path/to/file.py-- scan a specific file/security-scan ref=main-- scan diff against a branch or ref/security-scan full-- include all severities (not just HIGH/CRITICAL)- User pastes code inline and asks about security -- scan the pasted code
MCP Tools
The MCP server is named scanner. All tools are prefixed mcp__scanner__.
| Tool | When to Use |
|---|---|
mcp__scanner__scan_diff |
Default. Scan git changes (staged, unstaged, or vs a ref) |
mcp__scanner__scan_file |
User provides a file path to scan. Auto-scopes findings to lines changed vs HEAD when run inside a git repo (falls open on a clean file or non-repo path) |
mcp__scanner__scan_code |
User pastes code inline or asks about a snippet |
Tool Parameters
mcp__scanner__scan_diff
repo_path(string, optional): Path to git repo. Always set this to the absolute work-tree root of the repository you are working in — the value ofgit rev-parse --show-toplevel, not just your current working directory (which may be a subdirectory and would resolve the hash/scan-pass against the wrong root). The MCP server is a long-lived process whose own working directory may be a different checkout than yours — in a git worktree (e.g. a Conductor workspace) it is often the main repo, not your worktree. Passingrepo_pathpins the scan, the staged-diff hash, and the.scan-passwrite to your repo so the commit gate sees them. Omitting it falls back to the server's working directory, which is wrong outside that one checkout.ref(string, optional): Git ref to diff against (branch name, tag, SHA,HEAD~3). If empty, scans unstaged or staged changes.staged(bool, optional): If true, scan only staged changes (git diff --cached). Ignored whenrefis provided.
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.
- 6d ago First seen · 164 lines · 110 tokens per session scan A f18d0d6ca860
security-scan is a skill published in the GitHub repository ArmisSecurity/armis-appsec-mcp (6 stars, last pushed 24d ago), licensed Apache-2.0. It adds 110 tokens to every session and 2,752 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…