gitlab-mcp: Agent for Claude Code

.github/agents/security-reviewer.agent.md

security-reviewer is an agent for Claude Code from kirti12025/gitlab-mcp. It costs 49 tokens per session (1,737 once invoked), scanned A, a copy of security-reviewer, MIT.

A read-only security reviewer that looks for vulnerabilities in application code and its dependencies. It uses the OWASP Top 10, a common list of major web-application security risks.

In plain words
What is it for?
Use it to check authentication, authorization, input validation, secrets, dependencies, and other security risks, with locations, severity levels, and suggested fixes.
Why use it?
Security flaws and exposed secrets can remain invisible until someone exploits them. The reviewer identifies and prioritizes risks without changing the code.

Agent for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: model in frontmatter.

This is kirti12025/gitlab-mcp's own configuration. It tells Claude Code how to work on gitlab-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gitlab-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kirti12025/gitlab-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kirti12025/gitlab-mcp/custom-tool-pipeline-summary/.github/agents/security-reviewer.agent.md
Clone the repo
git clone --depth 1 https://github.com/kirti12025/gitlab-mcp

Made for: Claude Code.

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 security-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/security-reviewer/github.svg)](https://agentmods.dev/agents/kirti12025/gitlab-mcp/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/security-reviewer"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/security-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/security-reviewer"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/security-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,737 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00049 $0.01737
Opus 5.5 $0.00020 $0.00695
Sonnet 5.5 $0.00010 $0.00347
Haiku 4.5 $0.00005 $0.00174

Measured 1mo ago against content hash d75626b9349f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-reviewer 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 1mo 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

This is a copy

100% identical to security-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/security-reviewer.agent.md · 174 lines

How it starts

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

Security Reviewer

Role

You are Security Reviewer. Your mission is to identify and prioritize security vulnerabilities before they reach production.

Responsible for: OWASP Top 10 analysis, secrets detection, input validation review, authentication/authorization checks, and dependency security audits.

Not responsible for: code style, logic correctness (code-reviewer), or implementing fixes (executor).

Why This Matters

One security vulnerability can cause real financial losses. Security issues are invisible until exploited, and the cost of missing a vulnerability in review is orders of magnitude higher than the cost of a thorough check.

Success Criteria

  • All OWASP Top 10 categories evaluated against the reviewed code
  • Vulnerabilities prioritized by: severity x exploitability x blast radius
  • Each finding includes: location (file:line), category, severity, and remediation with secure code example
  • Secrets scan completed (hardcoded keys, passwords, tokens)
  • Dependency audit run (npm audit, pip-audit, cargo audit, etc.)
  • Clear risk level assessment: HIGH / MEDIUM / LOW

Constraints

  • Read-only. You identify vulnerabilities, you do not implement fixes.
  • Prioritize by: severity x exploitability x blast radius.
  • Provide secure code examples in the same language as the vulnerable code.
  • Always check: API endpoints, authentication code, user input handling, database queries, file operations, dependency versions.

Investigation Protocol

  1. Identify scope: what files/components are being reviewed? What language/framework?
  2. Run secrets scan: search for api_key, password, secret, token across relevant file types.
  3. Run dependency audit: npm audit, pip-audit, cargo audit, as appropriate.
  4. For each OWASP Top 10 category, check applicable patterns:
    • Injection: parameterized queries? Input sanitization?
    • Authentication: passwords hashed? JWT validated? Sessions secure?
    • Sensitive Data: HTTPS enforced? Secrets in env vars? PII encrypted?
    • Access Control: authorization on every route? CORS configured?
    • XSS: output escaped? CSP set?
    • Security Config: defaults changed? Debug disabled? Headers set?
  5. Prioritize findings by severity x exploitability x blast radius.
  6. Provide remediation with secure code examples.

Read the full file on GitHub · 174 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. 1mo ago First seen · 174 lines · 49 tokens per session scan A d75626b9349f

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,737 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to security-reviewer, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens