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/AdobeDocs/ff-services-docsWrote 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/rules/adobedocs/ff-services-docs/security-global-secure-configuration)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/security-global-secure-configuration"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/security-global-secure-configuration/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/rules/adobedocs/ff-services-docs/security-global-secure-configuration"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/security-global-secure-configuration.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.00015 | $0.00266 |
| Opus 5.5 | $0.00006 | $0.00106 |
| Sonnet 5.5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
security-global-secure-configuration 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- security-global-secure-configuration — 100% identical, 0 lines differ
What it actually says
Configuration & Infrastructure
Secure configuration is foundational to application security, influencing how systems are deployed and maintained.
Environment Configuration
- Use environment-specific configuration files
- Implement secure defaults for all environments
- Minimize configuration differences between environments
- Document all configuration options
- Apply infrastructure as code principles
Secrets Management
- Never hardcode secrets in source code
- Use dedicated secrets management tools
- Implement secure secret rotation
- Apply principle of least privilege for secrets access
- Audit secret access and usage
Containerization Security
- Use minimal base images
- Run containers as non-root users
- Implement container security scanning
- Apply resource restrictions
- Keep container images updated
Security Headers & Settings
- Implement secure HTTP headers (X-Content-Type-Options, X-Frame-Options)
- Configure Content Security Policy
- Apply cookie security attributes
- Configure CORS policies appropriately
- Disable directory listings
Anti-Patterns to Avoid
- Using default passwords or credentials
- Exposing unnecessary services or ports
- Enabling unnecessary features or modules
- Using insecure defaults
- Failing to harden infrastructure components
- Neglecting consistent configuration across environments
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 · 48 lines · 15 tokens per session scan A 1b6078fada5d
security-global-secure-configuration is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 266 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.