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 agentmods add rules/adobedocs/ff-services-docs/gatsby-configgit 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/gatsby-config)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/gatsby-config"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/gatsby-config.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.02615 |
| Opus 5 | $0.00006 | $0.01307 |
| Sonnet 5 | $0.00003 | $0.00523 |
| Haiku 4.5 | $0.00001 | $0.00262 |
Grade A, and why
gatsby-config 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 5d 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gatsby Configuration Navigation Rules
Overview
This rule documents the navigation patterns and best practices for the @adobe/gatsby-theme-aio theme in Gatsby configuration. Use these patterns to create and modify navigation structures in gatsby-config.js.
Navigation Components
1. Top Navigation (pages array)
pages: [
{
title: "Page Title", // Required: Display name in top nav
path: "/path/", // Required: URL path
}
]
- Used for main navigation bar items
- Limited to 5-7 items for clean UX
- Each item requires both
titleandpath - No nesting allowed by default (but see Menus below)
Top Navigation Dropdown Menus
You can create dropdown menus in the Global Navigation (header bar) by using the menu field instead of path:
pages: [
{
title: 'Adobe Analytics',
path: 'index.md'
},
{
title: 'Guides',
path: 'guides.md'
},
{
title: 'API Reference',
menu: [{
title: 'v2.0',
description: 'Version 2.0 of API', // optional
path: '2.0/api.index'
}, {
title: 'v1.4',
description: 'Version 1.4 of API', // optional
path: '1.4/api.index'
}]
}
]
Key Points:
- Use
menufield instead ofpathto create a Global navigation dropdown - Each menu item requires
titleandpath descriptionis optional but helpful for differentiating items- Common use cases:
- Multiple API versions
- Language or framework variations
- Related products or services
- Documentation sets
2. Side Navigation (subPages array)
subPages: [
{
title: "Section Title", // Required: Main section name
path: "/section-path/", // Required: Base URL for section
header: true, // Required: Makes it a main section
pages: [ // Required: Array of section items
// Pattern A: Regular page
{
title: "Page Title",
path: "/section-path/page/"
},
// Pattern B: Subsection with dropdown
{
title: "Subsection Title",
path: "/section-path/subsection/",
header: true, // Creates subsection
pages: [ // Creates dropdown
{
title: "Dropdown Item",
path: "/section-path/subsection/item/"
}
]
}
]
}
]
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.
- 5d ago First seen · 474 lines · 13 tokens per session scan A 48fcaafca752
gatsby-config is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,615 once invoked, about $0.0001 per session on Opus 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
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.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
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.