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/getting-started-docsgit clone --depth 1 https://github.com/AdobeDocs/ff-services-docsWhat 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.00002 | $0.04024 |
| Opus 5 | $0.00001 | $0.02012 |
| Sonnet 5 | $0.00000 | $0.00805 |
| Haiku 4.5 | $0.00000 | $0.00402 |
Grade A, and why
getting-started-docs 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 yesterday.
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 --url https://api.example.com How it starts
The opening of the file, as written. The whole thing — 591 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: How to add or edit Cursor rules in our project globs: alwaysApply: false
Getting Started Documentation Standards
This document defines the standards and guidelines for creating and maintaining Getting Started documentation in the Substance 3D API documentation.
Document Structure
Frontmatter
Every Getting Started document must include the following frontmatter:
---
title: [Clear, Action-Oriented Title]
description: [Concise description of the guide's purpose]
hideBreadcrumbNav: true
keywords:
- [Relevant keyword 1]
- [Relevant keyword 2]
---
Contributors Field
- Do NOT add contributors
Section requirements
-
Title (H1)
- Use clear, action-oriented titles
- Avoid "How to" or "Guide to" prefixes
- Example: "Authentication" instead of "How to Authenticate"
-
Overview (H2)
- Brief introduction (2-3 sentences)
- Clear statement of what the reader will learn
- No code examples in this section
-
Prerequisites (H2) - Optional
- Only include if there are specific requirements needed before starting
- Not required for quickstart guides or simple reference documentation
- When included, should contain:
- Bulleted list of requirements
- Links to related documentation
- Required accounts, credentials, or tools
- Example for when prerequisites are needed:
## Prerequisites This tutorial assumes you have: - An [Adobe Developer Console][1] account - A project with [required credentials][2] - [Required tool or software][3]
-
Main Content (H2+)
- Use clear, hierarchical headings (H2 → H3 → H4)
- Include practical examples
- Follow step-by-step format for tutorials
- Use code blocks with language specification
-
Code Examples
- Use triple backticks with language specification
- Include comments explaining complex operations
- Show both request and response examples
- Example:
```bash # Export credentials as environment variables export CLIENT_ID=<your_client_id>
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.
- yesterday First seen · 591 lines · 2 tokens per session scan A 71d6593c9625
getting-started-docs 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 2 tokens to every session and 4,024 once invoked, about $0.0000 per session on Opus 5. 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.