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/atlassian/forge-skills/_index-secrets-storagegit clone --depth 1 https://github.com/atlassian/forge-skillsWrote 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/atlassian/forge-skills/_index-secrets-storage)<a href="https://agentmods.dev/rules/atlassian/forge-skills/_index-secrets-storage"><img src="https://agentmods.dev/badge/rules/atlassian/forge-skills/_index-secrets-storage.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.00000 | $0.00445 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
_index-secrets-storage 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.
What it actually says
- Scope: Secret management, credential storage, sensitive data handling, and Forge storage API usage.
- Priority: Hardcoded secrets and credential mismanagement are common findings.
Key Forge Secrets/Storage Risks
- Hardcoded credentials: Basic auth headers, API keys, tokens embedded in source code.
- Improper secret storage: Using
storage.set()instead ofstorage.setSecret()for sensitive values. - PAT/API/OAuth token handling: Apps manually handling tokens instead of using Forge authentication.
- Secrets in logs: Credentials or tokens written to console or log outputs.
- Forge variables misuse: Not using encrypted Forge environment variables for secrets.
Subrules
- Hardcoded Secrets →
@forge-secrets-storage/hardcoded-secrets.mdc
Detection Heuristics
- Grep for
Basic [A-Za-z0-9+/]*={1,2}patterns in source (excluding node_modules). - Search for
storage.set()with keys containing 'secret', 'key', 'token', 'password', 'credential'. - Identify PAT/Atlassian account API token usage patterns:
Authorization: Bearerwith hardcoded values. - Look for
console.logor logging calls that include sensitive variable names.
Secure Patterns
- Use
storage.setSecret()andstorage.getSecret()for all sensitive values. - Use Forge environment variables with encryption for deployment secrets.
- Use External Auth for OAuth flows instead of manual token management.
- Implement secret redaction in all logging paths.
CWE References
- CWE-798: Use of Hard-coded Credentials
- CWE-312: Cleartext Storage of Sensitive Information
- CWE-532: Insertion of Sensitive Information into Log File
- CWE-522: Insufficiently Protected Credentials
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 · 47 lines · 0 tokens per session scan A 14999e3424cb
_index-secrets-storage is a cursor rule published in the GitHub repository atlassian/forge-skills (21 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 445 tokens. 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-30.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.