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.
git clone --depth 1 https://github.com/peteski22/agent-pragmaWrote 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.
[](https://agentmods.dev/agents/peteski22/agent-pragma/security)<a href="https://agentmods.dev/agents/peteski22/agent-pragma/security"><img src="https://agentmods.dev/badge/agents/peteski22/agent-pragma/security/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.
<a href="https://agentmods.dev/agents/peteski22/agent-pragma/security"><img src="https://agentmods.dev/badge/agents/peteski22/agent-pragma/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00051 | $0.00818 |
| Opus 5.5 | $0.00020 | $0.00327 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 78 lines · 51 tokens per session scan A 7dcc3e8e1b03
security is an agent published in the GitHub repository peteski22/agent-pragma (24 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 818 once invoked, about $0.0002 per session on Opus 5.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
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
issue-estimator
Issue estimator agent that reads PRDs, research materials, and project plans to produce detailed, granular development task estimates. Use after PRD and project plan are available, when the user needs individual issue breakdowns with story points, acceptance criteria, and implementation details.
code-writer
Code writer agent that implements development issues. Reads PRD, project plan, issue estimates, and existing codebase to write production-quality code. Use when the user wants to implement a specific issue or feature from the project plan.
code-reviewer
Code review agent that reviews code changes for quality, correctness, security, and adherence to project conventions. Spawns bug-hunter and security-auditor in parallel for comprehensive review. Merges into develop when all findings are resolved. Use after code is written, before merging.
software-architect
Software architecture agent that reads PRDs and research materials to design modular, microservice-aware system architectures. Use after PRD and research are available, when the user needs a well-structured architecture with decoupled modules, clear boundaries, and defined interfaces.