Atlassian Forge Skills supports Atlassian Forge, a platform for building and deploying apps that extend products such as Jira and Confluence. Its skills and MCP-backed tools help coding agents create Forge apps, review them before deployment, optimize usage, troubleshoot failures, and work with Forge APIs and the Atlassian Design System.
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/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-manifest-config)<a href="https://agentmods.dev/rules/atlassian/forge-skills/_index-manifest-config"><img src="https://agentmods.dev/badge/rules/atlassian/forge-skills/_index-manifest-config/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/atlassian/forge-skills/_index-manifest-config"><img src="https://agentmods.dev/badge/rules/atlassian/forge-skills/_index-manifest-config.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.00455 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
_index-manifest-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 10d 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: Manifest.yml configuration, permission scopes, CSP settings, runtime versions, and module definitions.
- Priority: Manifest misconfigurations are foundational security issues affecting all app operations.
Key Forge Manifest/Config Risks
- Excessive permission scopes: Requesting more scopes than needed violates least privilege.
- Unsafe CSP directives:
unsafe-inline,unsafe-evalinpermissions.content.scripts. - Deprecated Node.js runtime: Using EOL runtimes that lack security updates.
- Overly permissive module access: Modules exposed without appropriate restrictions.
- Missing data residency declarations: Required for certain compliance contexts.
Subrules
- Permission Scopes Review →
@forge-manifest-config/permission-scopes.mdc - Bad Practices with Egress Rule Entries ->
@forge-manifest-config/egress-url-entries.mdc - Content Security Policy →
@forge-manifest-config/content-security-policy.mdc
Detection Heuristics
- Parse manifest.yml and list all declared scopes; compare against actual API usage.
- Check
permissions.content.scriptsforunsafe-inlineorunsafe-eval. - Verify
app.runtime.nameuses a supported, non-deprecated Node.js version. - Review module definitions for function bindings and access patterns.
Manifest Review Checklist
- All scopes are justified by actual API calls in code
- No
unsafe-inlineorunsafe-evalin CSP (unless XSS mitigations documented) - Runtime version is current and supported
- External permissions use explicit domains (no wildcards)
- Web triggers have documented authentication strategy
- Remotes have appropriate operations and auth configured
CWE References
- CWE-16: Configuration
- CWE-732: Incorrect Permission Assignment
- CWE-269: Improper Privilege Management
- CWE-1188: Insecure Default Initialization of Resource
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.
- 10d ago First seen · 50 lines · 0 tokens per session scan A 11288c8e5b1d
_index-manifest-config is a cursor rule published in the GitHub repository atlassian/forge-skills (22 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 455 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.