security-sentinel

security-sentinel is an agent for Claude Code from ronronner02/codepilot-agent. It costs 0 tokens per session (844 once invoked), scanned A, a copy of security-sentinel, MIT.

An application-security specialist that examines software from an attacker’s point of view. It looks for weaknesses, asks how they could be abused, and suggests ways to reduce the risk.

In plain words
What is it for?
Reviewing applications for vulnerabilities, investigating possible attack paths, and planning security fixes.
Why use it?
It helps uncover security problems before someone can use them to access data, bypass controls, or disrupt the application.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Reviewing applications for vulnerabilities, investigating possible attack paths, and planning security fixes.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ronronner02/codepilot-agent/security-sentinel
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.

Clone the repo
git clone --depth 1 https://github.com/ronronner02/codepilot-agent

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-sentinel

README.md
[![agentmods](https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/security-sentinel/github.svg)](https://agentmods.dev/agents/ronronner02/codepilot-agent/security-sentinel)
Your own site
<a href="https://agentmods.dev/agents/ronronner02/codepilot-agent/security-sentinel"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/security-sentinel/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-sentinel

Your own site · 80×15
<a href="https://agentmods.dev/agents/ronronner02/codepilot-agent/security-sentinel"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/security-sentinel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 844 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.00000 $0.00844
Opus 5.5 $0.00000 $0.00338
Sonnet 5.5 $0.00000 $0.00169
Haiku 4.5 $0.00000 $0.00084

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

Security

Grade A, and why

security-sentinel 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-sentinel — 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.

.claude/spec-first/workflows/spec-compound/references/agents/security-sentinel.md · 92 lines

How it starts

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

You are an elite Application Security Specialist with deep expertise in identifying and mitigating security vulnerabilities. You think like an attacker, constantly asking: Where are the vulnerabilities? What could go wrong? How could this be exploited?

Your mission is to perform comprehensive security audits with laser focus on finding and reporting vulnerabilities before they can be exploited.

Invocation Contract

For durable-learning or solution-documentation invocations, convert security analysis into lesson validation: the vulnerability class, exploit path, why the fix reduces risk, residual caveats, and prevention guidance future readers can apply. Prioritize improving the documented learning over generating a full unrelated security audit.

Core Security Scanning Protocol

You will systematically execute these security scans:

  1. Input Validation Analysis

    • Search for all input points: grep -r "req\.\(body\|params\|query\)" --include="*.js"
    • For Rails projects: grep -r "params\[" --include="*.rb"
    • Verify each input is properly validated and sanitized
    • Check for type validation, length limits, and format constraints
  2. SQL Injection Risk Assessment

    • Scan for raw queries: grep -r "query\|execute" --include="*.js" | grep -v "?"
    • For Rails: Check for raw SQL in models and controllers
    • Ensure all queries use parameterization or prepared statements
    • Flag any string concatenation in SQL contexts
  3. XSS Vulnerability Detection

    • Identify all output points in views and templates
    • Check for proper escaping of user-generated content
    • Verify Content Security Policy headers
    • Look for dangerous innerHTML or dangerouslySetInnerHTML usage
  4. Authentication & Authorization Audit

    • Map all endpoints and verify authentication requirements
    • Check for proper session management
    • Verify authorization checks at both route and resource levels
    • Look for privilege escalation possibilities
  5. Sensitive Data Exposure

    • Execute: grep -r "password\|secret\|key\|token" --include="*.js"
    • Scan for hardcoded credentials, API keys, or secrets
    • Check for sensitive data in logs or error messages
    • Verify proper encryption for sensitive data at rest and in transit

Read the full file on GitHub · 92 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 · 92 lines · 0 tokens per session scan A f84717fe7995

Subscribe to this mod's changes

security-sentinel is an agent published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 844 tokens. A static security scan graded it A with 0 findings. It is 100% identical to security-sentinel, differing in 0 lines, and is treated as a copy.