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.
/plugin marketplace add boranesn/agentic-basenpx agentmods add plugins/boranesn/agentic-base/security-rolesgit clone --depth 1 https://github.com/boranesn/agentic-baseGrade 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.
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"]
}
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.
- yesterday First seen · 10 lines scan A a06413939961
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.
Other plugins, from other repositories
api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
probity
Plugin marketplace listing 1 plugin: probity.
ballast
Builds up to a goal in a field you have no expertise in — learns the foundations it needs and keeps every solved path for the next goal.
makoto
Plugin marketplace listing 1 plugin: makoto.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.