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 skills add easingthemes/dx-aem-flow --skill dx-securitygit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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/skills/easingthemes/dx-aem-flow/dx-security)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-security"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-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/skills/easingthemes/dx-aem-flow/dx-security"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-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.00040 | $0.02249 |
| Opus 5.5 | $0.00016 | $0.00900 |
| Sonnet 5.5 | $0.00008 | $0.00450 |
| Haiku 4.5 | $0.00004 | $0.00225 |
Grade A, and why
dx-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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You perform a security audit of the codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, dependency vulnerabilities, and hardening gaps.
1. Determine Scope
changes(default) — audit only files changed since base branchfull— audit the entire codebase
Get the file list:
# changes mode
BASE=$(git merge-base $(git symbolic-ref refs/remotes/origin/HEAD --short 2>/dev/null || echo origin/main) HEAD)
git diff --name-only $BASE..HEAD
# full mode
find . -type f \( -name '*.js' -o -name '*.ts' -o -name '*.java' -o -name '*.py' -o -name '*.jsx' -o -name '*.tsx' -o -name '*.xml' -o -name '*.yaml' -o -name '*.yml' -o -name '*.json' \) | grep -v node_modules | grep -v target
Read shared/security-checklist.md for the full checklist reference.
2. Three-Tier Boundary System
ALWAYS DO (Non-negotiable)
These must be present in every project. Flag if missing:
- All external input validated at system boundaries (API endpoints, form handlers)
- Database queries parameterized — no string concatenation with user data
- Output encoded to prevent XSS (framework auto-escaping enabled)
- HTTPS for all external communication
- Passwords hashed with bcrypt/scrypt/argon2 (not MD5/SHA-1)
- Security headers set: CSP, HSTS, X-Frame-Options, X-Content-Type-Options
- Session cookies: httpOnly, secure, sameSite
- Dependency audit clean (
npm audit/mvn dependency-check)
ASK FIRST (Flag for team review)
These require explicit team decision:
- New authentication flows or authorization logic changes
- Storage of additional sensitive data categories
- New third-party service integrations
- CORS configuration changes
- File upload functionality additions
- Rate limiting or throttling changes
- Permission or role elevation logic
NEVER DO (Hard blocks)
Flag these as Critical — merge-blocking:
- Secrets committed to version control
- Sensitive data in logs (passwords, tokens, card numbers, PII)
- Client-side validation as the only security boundary
eval()orinnerHTMLwith untrusted data- Auth tokens in localStorage (use httpOnly cookies)
- Stack traces exposed to users in production
- Security headers disabled "for convenience"
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 Changed · -1 lines · -2 tokens per session 6c2e8c207ff9
- 1mo ago First seen · 239 lines · 42 tokens per session scan A d2fa468eac4e
dx-security is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 2,249 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…