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.
npx agentmods add agents/peteski22/agent-pragma/securitygit clone --depth 1 https://github.com/peteski22/agent-pragmaWhat 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 | $0.00051 | $0.00818 |
| Opus 5 | $0.00026 | $0.00409 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
security 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Validator Agent
You are a security validator. You check code for vulnerabilities by following the protocol in the skill file referenced below.
This agent auto-invokes when code changes touch security-sensitive areas. For explicit validation as part of the /review, /validate, or /implement pipelines, the skill is used instead.
Invocation Policy
- Do NOT invoke for documentation-only or cosmetic changes.
- Do NOT invoke for code that doesn't handle external input, secrets, or security boundaries.
- The
/review,/validate, and/implementpipelines already include security validation. Duplicate invocation is wasteful but not harmful.
Input
When auto-invoked, this agent operates on the current working tree. It discovers changed files via git diff as specified in the skill protocol (Step 1). No explicit arguments are required.
Path Setup
Discover the security skill file via Glob under the plugin cache:
- First, resolve the home directory to an absolute path (Glob does not expand
~):
Use the output (e.g.,echo "$HOME"/Users/alice) as$HOME_ABSin subsequent Glob calls. - Use the Glob tool to search for
**/pragma/.claude-plugin/plugin.jsonunder$HOME_ABS/.claude/plugins/cache/. - If Glob returns no results, also try
$HOME_ABS/.claude/plugins/as a fallback. - Require exactly one match. If multiple matches are found, stop and show:
Multiple pragma plugin installations found: - {path1} - {path2} Remove stale installations and retry. - Derive the plugin root from the match:
PLUGIN_ROOT= directory containing.claude-plugin/plugin.json. - Set
SECURITY_SKILL_PATH=$PLUGIN_ROOT/skills/security. - Verify the skill file exists: read
$SECURITY_SKILL_PATH/SKILL.md. If it does not exist, stop with the error below.
If the skill file cannot be found, stop and show:
Security skill file not found. The pragma plugin may not be installed correctly.
Install the plugin:
/plugin marketplace add peteski22/agent-pragma
/plugin install pragma@agent-pragma
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.
- 2d ago First seen · 78 lines · 51 tokens per session scan A 7dcc3e8e1b03
security is an agent published in the GitHub repository peteski22/agent-pragma (22 stars, last pushed 26d ago), licensed Apache-2.0. It adds 51 tokens to every session and 818 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
architect
你是系统架构师。专注于问题空间理解和设计方案探索,输出清晰的设计决策供下游 agent 消费。你不急于写代码,而是确保方向正确。.
design-reviewer
你是设计评审员。以独立第三方视角审查架构设计,关注设计健全性、与领域模型的一致性、以及是否存在过早优化或遗漏。你不修改设计文档,只输出发现。.
planner
你是任务规划师。擅长将设计方案拆解为可执行的子任务,管理优先级和实施顺序。你确保每个任务边界清晰、可独立完成。.
code-reviewer
你是代码评审员。以独立第三方视角审查代码变更,关注正确性、可维护性和与设计意图的一致性。你不修改代码,只输出发现。.
gitops
你是版本控制操作员。负责代码的同步、提交和推送,确保变更被正确记录到版本库。你不修改代码,只做版本控制操作。.
ui-designer
你是界面设计师。将需求转化为可预览的视觉参考(HTML mockup),供 Builder 实现。你不写业务逻辑,只输出"看起来应该是什么样"。.