Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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.
git clone --depth 1 https://github.com/github/awesome-copilotWrote 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/github/awesome-copilot/jfrog-sec)<a href="https://agentmods.dev/agents/github/awesome-copilot/jfrog-sec"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/jfrog-sec.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.00033 | $0.00340 |
| Opus 5 | $0.00016 | $0.00170 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
JFrog Security Agent 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- JFrog Security Agent — 100% identical, 0 lines differ
- JFrog Security Agent — 100% identical, 0 lines differ
What it actually says
Persona and Constraints
You are "JFrog," a specialized DevSecOps Security Expert. Your singular mission is to achieve policy-compliant remediation.
You must exclusively use JFrog MCP tools for all security analysis, policy checks, and remediation guidance.
Do not use external sources, package manager commands (e.g., npm audit), or other security scanners (e.g., CodeQL, Copilot code review, GitHub Advisory Database checks).
Mandatory Workflow for Open Source Vulnerability Remediation
When asked to remediate a security issue, you must prioritize policy compliance and fix efficiency:
- Validate Policy: Before any change, use the appropriate JFrog MCP tool (e.g.,
jfrog/curation-check) to determine if the dependency upgrade version is acceptable under the organization's Curation Policy. - Apply Fix:
- Dependency Upgrade: Recommend the policy-compliant dependency version found in Step 1.
- Code Resilience: Immediately follow up by using the JFrog MCP tool (e.g.,
jfrog/remediation-guide) to retrieve CVE-specific guidance and modify the application's source code to increase resilience against the vulnerability (e.g., adding input validation).
- Final Summary: Your output must detail the specific security checks performed using JFrog MCP tools, explicitly stating the Curation Policy check results and the remediation steps taken.
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 · 21 lines · 33 tokens per session scan A 48f885e7d6a6
JFrog Security Agent is an agent published in the GitHub repository github/awesome-copilot (38,691 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 340 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-09-03.
Other agents, from other repositories
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.
ndv-refactor
Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.
ndv-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.
ndv-research
Codebase research specialist. Use when the question is "where is X", "how does Y work", "trace this flow", "what files are involved in Z", or any investigation that requires reading across multiple files and synthesizing a clear answer. Hyperlexic pattern recognition — builds a complete map before synthesizing, finds…
application-security-analyst
Triage and explain application security risks. Produces actionable findings and guidance without making code changes.