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/md-lint)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/md-lint"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/md-lint/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/md-lint"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/md-lint.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.00000 | $0.02147 |
| Opus 5.5 | $0.00000 | $0.00859 |
| Sonnet 5.5 | $0.00000 | $0.00429 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade A, and why
md-lint scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.example.com/endpoint \ How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Linting Rules
Overview
This document outlines the linting rules and best practices for maintaining high-quality documentation in our project.
Linting Process
Running the Linter
⚠️ Prerequisite Check: Docker Availability
Before running the linter, always check if Docker is running:
# Check Docker status
docker info > /dev/null 2>&1
# If the above command fails, Docker is not running
if [ $? -ne 0 ]; then
echo "❌ Docker is not running!"
echo "Please start Docker Desktop and try again."
echo ""
read -p "Continue with manual linting fixes? (Y/N): " -n 1 -r
echo
if [[ ! $REPLY =~ ^[Yy]$ ]]; then
echo "Exiting. Please start Docker and run 'yarn lint' again."
exit 1
fi
echo "Proceeding with manual linting fixes..."
fi
Then run the linter:
yarn lint
Note: This command requires Docker to be installed and running. If Docker is not available, you can:
- Start Docker Desktop manually
- Or use the manual linting fixes described in the "Automated Fixes" section below
The linter checks:
- Markdown files (markdownlint)
- YAML files (yamllint)
- JSON files (jsonlint)
- Security issues (gitleaks)
Link Validation
After successful linting, validate all links in the documentation:
yarn test:links
The link validator checks:
- Internal links (anchors, file references)
- External links (URLs)
- Relative path references
- Broken or inaccessible links
Note: Link validation should be run AFTER linting is successful, as it depends on properly formatted markdown files.
Link Validation Errors and Resolution
Common Link Issues:
-
Broken Internal Links
- Missing anchor references
- Incorrect file paths
- Case sensitivity issues
-
Broken External Links
- URLs that no longer exist
- Network connectivity issues
- Rate limiting from external sites
-
Relative Path Issues
- Incorrect relative paths
- Missing files referenced in links
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 · 379 lines · 2,147 tokens per session scan A cecac6c9dc66
md-lint is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,147 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).