skills
diff --git a/‎.devcontainer/devcontainer.json‎
Lines changed: 5 additions & 2 deletions b/‎.devcontainer/devcontainer.json‎
Lines changed: 5 additions & 2 deletions
diff --git a/‎.gitignore‎
Lines changed: 14 additions & 1 deletion b/‎.gitignore‎
Lines changed: 14 additions & 1 deletion
diff --git a/‎CONTRIBUTING.md‎
Lines changed: 39 additions & 25 deletions b/‎CONTRIBUTING.md‎
Lines changed: 39 additions & 25 deletions
@@ -9,10 +9,13 @@
         "redhat.vscode-yaml",
         "golang.go",
         "vitest.explorer"
-      ]
+      ],
+      "settings": {
+        "vitest.logLevel": "error"
+      }
     }
   },
-  "postCreateCommand": "pip install -r requirements.txt; npm install --prefix Season-3/",
+  "postCreateCommand": "pip install --break-system-packages -r requirements.txt; npm install --prefix Season-3/; npm install --prefix Season-4/; chmod +x Season-4/bin/prodbot.js && mkdir -p ~/.local/bin && ln -sf \"$(pwd)/Season-4/bin/prodbot.js\" ~/.local/bin/prodbot && echo 'export PATH=\"$HOME/.local/bin:$PATH\"' >> ~/.bashrc && export PATH=\"$HOME/.local/bin:$PATH\"",
   "features": {
     "ghcr.io/devcontainers/features/python:1.7.1": {},
     "ghcr.io/devcontainers/features/node:1": {}
 
@@ -1,3 +1,14 @@
+### SEASON 4 ###
+# ProdBot sandbox — runtime-generated files, auto-created by prodbot.js
+Season-4/Level-1/prodbot-activities/*
+!Season-4/Level-1/prodbot-activities/.gitkeep
+Season-4/Level-2/prodbot-activities/*
+!Season-4/Level-2/prodbot-activities/.gitkeep
+Season-4/Level-3/prodbot-activities/*
+!Season-4/Level-3/prodbot-activities/.gitkeep
+Season-4/Level-4/prodbot-activities/*
+!Season-4/Level-4/prodbot-activities/.gitkeep
+
 ### VSCODE ###
 .vscode/*
 !.vscode/settings.json
@@ -31,6 +42,7 @@ downloads/
 eggs/
 .eggs/
 lib/
+!Season-4/lib/
 lib64/
 parts/
 sdist/
@@ -303,4 +315,5 @@ Thumbs.db
 modules.order
 Module.symvers
 Mkfile.old
-dkms.conf
+dkms.conf.vite/
+.vite/
@@ -1,51 +1,65 @@
 # Secure Code Game Contribution Guideline
 
-Thank you for your interest in contributing to the Secure Code Game. Let's collaborate and bring your ideas to life for a lasting impact on the global cybersecurity scene. Follow these guidelines:
+Thank you for your interest in contributing to the Secure Code Game. Let's collaborate and bring your ideas to life for a lasting impact on the global cybersecurity scene. Contributions fall into two tracks depending on where your idea fits best.
 
-## 1. Review current proposals
+---
 
-Make sure your idea was not already discussed. Consider joining [existing proposals](https://github.com/skills/secure-code-game/discussions/categories/new-level-proposals) and contributing collaboratively instead of duplicating efforts.
-
-## 2. Create a new proposal
+## 🤖 Artificial Intelligence (Seasons 3, 4 & beyond)
 
-Start a [new discussion](https://github.com/skills/secure-code-game/discussions/new?category=new-level-proposals) by providing, at the very least, the following elements:
+These seasons focus on AI security, from prompt injection in LLM applications (Season 3) to agentic workflows, multi-agent communications, and tool-use vulnerabilities in ProdBot (Season 4). If you have ideas for extending ProdBot with the latest advances in artificial intelligence towards Season 5, we want to hear from you.
 
-- **Vulnerability:** Propose a specific vulnerability that you would like to include in the game.
-- **Programming Language:** Specify the programming language you want to use for implementing the code.
-- **Scenario:** Describe the scenario where the vulnerability will be introduced.
+Contributions in this track could include new attack vectors, defensive techniques, agent architectures, MCP integrations, skill plugins, or entirely new capabilities that reflect the evolving AI security landscape. Make sure your contribution aligns with ProdBot's existing architecture in `Season-4/`.
 
-**Example:**
+---
 
-👋 Hi, I would like to contribute a DOM-based Cross-Site Scripting (XSS) vulnerability in JavaScript. The scenario involves an online forum where users can write responses through a text box, but input sanitization wasn't implemented securely. An attacker could exploit this by injecting malicious code, for example `</>`.
+## 🛡️ Secure Coding (Seasons 1 & 2)
 
-## Increase your proposal’s chances
+These seasons focus on finding and fixing traditional security vulnerabilities across multiple programming languages. If your idea involves a specific vulnerability class and language, this is the right track.
 
-To increase the chances of your proposal being merged into the game, consider suggesting a vulnerability and programming language combination that we haven't yet included in the game or rejected in past discussions. While we welcome all contributions, you will have more chances for these popular vulnerabilities and programming languages:
+To increase the chances of your proposal being merged, consider suggesting a vulnerability and programming language combination that we haven't yet included or rejected in past discussions. While we welcome all contributions, you will have more chances for these popular vulnerabilities and languages:
 
 - **TypeScript/JavaScript:** Server-Side Request Forgery (SSRF), Broken Access Control, Cross-Site Request Forgery (CSRF)
 - **C#:** Server-Side Request Forgery (SSRF), Remote Code Execution, Insecure Deserialization, Cross-Site Request Forgery (CSRF)
 - **Java:** Broken Access Control, Remote Code Execution, Insecure Deserialization
 
-Please feel free to propose other vulnerabilities and programming languages or frameworks as well. For those looking for community feedback on an idea before opening a discussion, or for other collaborators and beta-testers, you can join our vibrant [Slack community](https://gh.io/securitylabslack) and engage in the [#secure-code-game](https://ghsecuritylab.slack.com/archives/C05DH0PSBEZ) channel.
+Please feel free to propose other vulnerabilities, languages, or frameworks as well.
+
+---
+
+## How to contribute
+
+The following process applies to both tracks.
+
+### 1. Review current proposals
+
+Make sure your idea was not already discussed. Consider joining [existing proposals](https://github.com/skills/secure-code-game/discussions/categories/new-level-proposals) and contributing collaboratively instead of duplicating efforts.
+
+### 2. Create a new proposal
+
+Start a [new discussion](https://github.com/skills/secure-code-game/discussions/new?category=new-level-proposals) by providing, at the very least, the following elements:
+
+- **Vulnerability:** Propose a specific vulnerability that you would like to include in the game.
+- **Programming Language:** Specify the programming language you want to use for implementing the code.
+- **Scenario:** Describe the scenario where the vulnerability will be introduced.
+
+**Example:**
+
+> 👋 Hi, I would like to contribute a DOM-based Cross-Site Scripting (XSS) vulnerability in JavaScript. The scenario involves an online forum where users can write responses through a text box, but input sanitization wasn't implemented securely. An attacker could exploit this by injecting malicious code, for example `</>`.
 
-## 3. Submit a Pull Request
+### 3. Submit a Pull Request
 
-Once your proposal receives approval in [GitHub Discussions](https://github.com/skills/secure-code-game/discussions/categories/new-level-proposals), you can proceed to submit a pull request (PR) to the game's [repository](https://github.com/skills/secure-code-game). Ensure that your PR follows the [file structure](https://github.com/skills/secure-code-game) conventions of the existing game levels. For example, if you're submitting a DOM-based Cross-Site Scripting (XSS) vulnerability in JavaScript, your PR should include the following files:
+Once your proposal receives approval in [GitHub Discussions](https://github.com/skills/secure-code-game/discussions/categories/new-level-proposals), submit a pull request (PR) following the [file structure](https://github.com/skills/secure-code-game) conventions of the existing levels. Ensure your PR includes all necessary files such as a storyline, vulnerable code, hints, solution, and tests.
 
-- storyline
-- code.js
-- hack.js
-- hint.js
-- solution.js
-- tests.js
-- dependencies in requirements.txt
+---
 
 ## Credit
 
 We highly appreciate your contribution to the Secure Code Game. As a token of our gratitude, we will prominently display your name at the beginning of the level you contribute, along with a clickable URL to your GitHub profile or another social media platform of your choice.
 
+---
+
 ## Additional Information
 
-- If you have any questions or need assistance, don't hesitate to ask for help in [GitHub Discussions](https://github.com/skills/secure-code-game/discussions/categories/new-level-proposals) or from our [Slack community](https://gh.io/securitylabslack) at the [#secure-code-game](https://ghsecuritylab.slack.com/archives/C05DH0PSBEZ) channel.
+If you have any questions or need assistance, don't hesitate to ask for help in [GitHub Discussions](https://github.com/skills/secure-code-game/discussions/categories/new-level-proposals) or from our [Slack community](https://gh.io/securitylabslack) at the [#secure-code-game](https://ghsecuritylab.slack.com/archives/C05DH0PSBEZ) channel.
 
-We appreciate your dedication to improving software security through the Secure Code Game 🎮 🔐
+We appreciate your dedication to improving software security through the Secure Code Game 🎮 🔐