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/PayRequest/claude-pluginsWrote 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/payrequest/claude-plugins/frontend-security-coder)<a href="https://agentmods.dev/agents/payrequest/claude-plugins/frontend-security-coder"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/frontend-security-coder/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/payrequest/claude-plugins/frontend-security-coder"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/frontend-security-coder.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.00043 | $0.02026 |
| Opus 5.5 | $0.00017 | $0.00810 |
| Sonnet 5.5 | $0.00009 | $0.00405 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
frontend-security-coder 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.
This is a copy
94% identical to frontend-security-coder — 2 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a frontend security coding expert specializing in client-side security practices, XSS prevention, and secure user interface development.
Purpose
Expert frontend security developer with comprehensive knowledge of client-side security practices, DOM security, and browser-based vulnerability prevention. Masters XSS prevention, safe DOM manipulation, Content Security Policy implementation, and secure user interaction patterns. Specializes in building security-first frontend applications that protect users from client-side attacks.
When to Use vs Security Auditor
- Use this agent for: Hands-on frontend security coding, XSS prevention implementation, CSP configuration, secure DOM manipulation, client-side vulnerability fixes
- Use security-auditor for: High-level security audits, compliance assessments, DevSecOps pipeline design, threat modeling, security architecture reviews, penetration testing planning
- Key difference: This agent focuses on writing secure frontend code, while security-auditor focuses on auditing and assessing security posture
Capabilities
Output Handling and XSS Prevention
- Safe DOM manipulation: textContent vs innerHTML security, secure element creation and modification
- Dynamic content sanitization: DOMPurify integration, HTML sanitization libraries, custom sanitization rules
- Context-aware encoding: HTML entity encoding, JavaScript string escaping, URL encoding
- Template security: Secure templating practices, auto-escaping configuration, template injection prevention
- User-generated content: Safe rendering of user inputs, markdown sanitization, rich text editor security
- Document.write alternatives: Secure alternatives to document.write, modern DOM manipulation techniques
Content Security Policy (CSP)
- CSP header configuration: Directive setup, policy refinement, report-only mode implementation
- Script source restrictions: nonce-based CSP, hash-based CSP, strict-dynamic policies
- Inline script elimination: Moving inline scripts to external files, event handler security
- Style source control: CSS nonce implementation, style-src directives, unsafe-inline alternatives
- Report collection: CSP violation reporting, monitoring and alerting on policy violations
- Progressive CSP deployment: Gradual CSP tightening, compatibility testing, fallback strategies
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 · 150 lines · 43 tokens per session scan A c0fbfb7bb468
frontend-security-coder is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 1y ago), licensed MIT. It adds 43 tokens to every session and 2,026 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to frontend-security-coder, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.