security-roles

A security plugin that adds authentication and security roles plus automated checks before and after code changes. It can use built-in rules and, when installed, Semgrep, a tool that searches code for known security patterns.

In plain words
What is it for?
Use it to run security gates around coding work, review authentication-related changes, rescan modified code, and track unresolved security findings.
Why use it?
It helps block writing when a pre-change scan finds problems and requires another scan afterward. It prevents ending a session with unresolved findings, while a clean scan does not guarantee secure code.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add boranesn/agentic-base
agentmods
npx agentmods add plugins/boranesn/agentic-base/security-roles
Clone the repo
git clone --depth 1 https://github.com/boranesn/agentic-base

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

security-roles 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 yesterday.

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.

plugins/security-roles/.claude-plugin/plugin.json · 10 lines

What it actually says

{
  "name": "security-roles",
  "version": "0.1.2",
  "description": "Auth/Security ajanları + deterministik güvenlik taraması gate'i (yazım öncesi blok, yazım sonrası yeniden tarama, çözülmemiş bulguyla oturum bitirme engeli). Yerleşik kural seti minimal bir tabandır; semgrep kuruluysa ek katman olarak koşulur — temiz tarama, güvenli kod garantisi değildir.",
  "author": {
    "name": "Boran"
  },
  "dependencies": ["core-loop"]
}
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. yesterday First seen · 10 lines scan A a06413939961

Subscribe to this mod's changes

security-roles is a plugin published in the GitHub repository boranesn/agentic-base (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.