_index-auditing

_index-auditing is a cursor rule for coding agents from atlassian/forge-skills. It costs 0 tokens per session (400 once invoked), scanned A, original, Apache-2.0.

A rule index for checking logging, error handling, and security scanning in Atlassian Forge apps. SAST means automated source-code scanning for security problems.

In plain words
What is it for?
Use it to review console and logger calls, error responses, audit trails, and SAST configurations covering Forge SQL, storage, resolvers, and related patterns.
Why use it?
It helps detect leaked secrets or personal data, overly detailed errors, missing audit records, and scanners that overlook Forge-specific risks.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/atlassian/forge-skills/_index-auditing
Clone the repo
git clone --depth 1 https://github.com/atlassian/forge-skills

Wrote 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.

agentmods badge for _index-auditing

README.md
[![agentmods](https://agentmods.dev/badge/rules/atlassian/forge-skills/_index-auditing.svg)](https://agentmods.dev/rules/atlassian/forge-skills/_index-auditing)
Your own site
<a href="https://agentmods.dev/rules/atlassian/forge-skills/_index-auditing"><img src="https://agentmods.dev/badge/rules/atlassian/forge-skills/_index-auditing.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00400
Opus 5 $0.00000 $0.00200
Sonnet 5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

Measured 4d ago against content hash f0c2c7e6afc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

_index-auditing 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 4d 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.

skills/forge-security-review/assets/security-rules/forge-auditing/_index-auditing.mdc · 48 lines

What it actually says

  • Scope: Logging practices, error handling, static analysis tooling, and observability for Forge apps.

Key Forge Auditing Concerns

  • Sensitive data in logs: Tokens, credentials, PII written to console or log outputs.
  • Verbose error messages: Stack traces or internal details exposed to users.
  • Missing security logging: Lack of audit trails for sensitive operations.
  • SAST tool configuration: Ensuring Forge-specific patterns are covered by scanners.

Subrules

  • Logging Security → @forge-auditing/logging-security.mdc
  • Error Handling → @forge-auditing/error-handling.mdc
  • Static Analysis for Forge → @forge-auditing/static-analysis-forge.mdc

Detection Heuristics

  • Search for console.log, console.error, logger.* calls that include sensitive variable names.
  • Check error handlers for information leakage (stack traces, internal paths, query details).
  • Verify SAST configurations include Forge-specific rules (SQL API, storage, resolvers).

SAST Tools for Forge

  • Semgrep: Custom rules for Forge patterns (sql.executeRaw, dangerouslySetInnerHTML, etc.)
  • FSRT: Forge Static Review Tool for AuthN/AuthZ and secrets scanning
  • Snyk: SCA for dependency vulnerabilities

Forge-Specific Logging Concerns

  • Lambda logs are aggregated; ensure tenant context doesn't leak across log entries.
  • Forge provides built-in logging via console; review what's captured.
  • Error responses should not include internal implementation details.

CWE References

  • CWE-778: Insufficient Logging
  • CWE-209: Information Exposure Through an Error Message
  • CWE-117: Improper Output Neutralization for Logs
  • CWE-532: Insertion of Sensitive Information into Log File
Changes

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.

  1. 4d ago First seen · 48 lines · 0 tokens per session scan A f0c2c7e6afc4

Subscribe to this mod's changes

_index-auditing is a cursor rule published in the GitHub repository atlassian/forge-skills (20 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 400 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.