forge-security-review

forge-security-review is a skill for Claude Code from atlassian/forge-skills. It costs 74 tokens per session (1,441 once invoked), scanned A, original, Apache-2.0.

A guided security-review skill for Atlassian Forge apps. It examines the app’s code and configuration and produces evidence-based findings about security weaknesses.

In plain words
What is it for?
Use it for Forge security audits, vulnerability assessments, penetration-test-style code reviews, authorization checks, web-trigger checks, and related investigations.
Why use it?
It helps find problems such as missing access checks, unsafe input handling, and weak tenant separation without loading every review rule unnecessarily.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forge-skills plugin — 6 skills, 2 MCP servers shipped together

Good fit Use it for Forge security audits, vulnerability assessments, penetration-test-style code reviews, authorization checks, web-trigger checks, and related investigations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atlassian/forge-skills/forge-security-review
About the project

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.

atlassian/forge-skills · 22 stars · on GitHub · developer.atlassian.com

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.

Any agent
npx skills add atlassian/forge-skills --skill forge-security-review
Clone the repo
git clone --depth 1 https://github.com/atlassian/forge-skills

Made for: Claude Code.

Or install forge-skills, the plugin that ships this one along with the rest of its 6 skills, 2 MCP servers.

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 forge-security-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/atlassian/forge-skills/forge-security-review/github.svg)](https://agentmods.dev/skills/atlassian/forge-skills/forge-security-review)
Your own site
<a href="https://agentmods.dev/skills/atlassian/forge-skills/forge-security-review"><img src="https://agentmods.dev/badge/skills/atlassian/forge-skills/forge-security-review/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.

agentmods 80×15 button for forge-security-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/atlassian/forge-skills/forge-security-review"><img src="https://agentmods.dev/badge/skills/atlassian/forge-skills/forge-security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Prompt Injection · line 81
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
How audits are shown
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.1 $0.00074 $0.01441
Opus 5 $0.00037 $0.00720
Sonnet 5 $0.00015 $0.00288
Haiku 4.5 $0.00007 $0.00144

Measured 9d ago against content hash b22701c086ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

forge-security-review 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 9d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/run_static_analysis.ps1, scripts/run_static_analysis.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/SKILL.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Forge Security Review

Runs a Forge-focused white-box security review and reports validated findings with exploitability, impact, evidence, and remediation guidance.

Token-Efficient Default

Use manifest-driven routing by default to reduce token usage. Do not load every rule file up front.

Rule Assets

The review rules are packaged with this skill under assets/security-rules/:

  • Global baseline: assets/security-rules/_global-forge.mdc
  • Category indexes: assets/security-rules/forge-*/_index-*.mdc
  • Category deep checks: assets/security-rules/forge-*/*.mdc

Execution Mandate

When this skill is triggered:

  1. Run static analysis first from this skill directory:
  • scripts/run_static_analysis.sh <forge-project-root-directory>
  • use .ps1 script for windows
  1. Read manifest.yml first before any deep code review.
  2. Load assets/security-rules/_global-forge.mdc first.
  3. Load only relevant category index rules based on manifest and code signals.
  4. Load deep subrules only when the matching detection heuristics are triggered by real code patterns.
  5. Perform an evidence-based security review across:
    • AuthN/AuthZ
    • Injection and input validation
    • Tenant isolation and cross-tenant leakage
    • Secrets and storage
    • Egress/remotes/CSP and manifest permissions
    • Public entry points (web triggers)
    • Agent and miscellaneous Forge security risks
  6. Do not modify app code unless the user explicitly requests fixes.
  7. Write all scan outputs and generated artifacts to security-audit-artifacts/.

Rule Routing Workflow

Phase 1: Reconnaissance (Mandatory)

Read manifest.yml first and extract:

  • permissions.scopes
  • permissions.external.fetch
  • permissions.content.scripts
  • modules (resolver/webtrigger/scheduledTrigger/rovo/etc.)
  • remotes
  • app.runtime.name

Build an execution map:

  • UI modules -> bridge calls -> resolvers/functions
  • External entry points (web triggers, events, schedules)
  • api.asUser() vs api.asApp() paths
  • Outbound fetch destinations

Read the full file on GitHub · 158 lines

Files

What ships with it

35 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 158 lines · 74 tokens per session scan A b22701c086ba

Subscribe to this mod's changes

forge-security-review is a skill published in the GitHub repository atlassian/forge-skills (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 1,441 once invoked, about $0.0004 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-30.