Skip to main content

reverse-skill-router

Use the reverse-skill repository from Codex for authorized reverse engineering, security analysis, CTF, and defensive testing tasks. Requires the reverse-skill repository to be available as the current workspace or an explicitly supplied local path.

インストールへ移動

ソース情報

リポジトリ
zhaoxuya520/reverse-skill
ソースの最終更新活動
2026年9月3日 12:19
検出された SKILL.md の言語
英語
スター
36,816
フォーク
5,113

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
reverse-skill-router
description
Use the reverse-skill repository from Codex for authorized reverse engineering, security analysis, CTF, and defensive testing tasks. Requires the reverse-skill repository to be available as the current workspace or an explicitly supplied local path.
# Reverse Skill Codex adapter This plugin is an optional Codex entry point. The repository remains the canonical, client-neutral implementation. When the current workspace is the `reverse-skill` repository: 1. Read `RULES.md` at the repository root. 2. Run the platform-native `skills/scripts/master-route` entry with the user's task to select the PRIMARY skill from `skills/config/routing.json`. 3. Before any target action, create and validate `work/<case>/scope.md` with the platform-native `case-init` and `case-guard` scripts. 4. Open the selected `skills/<PRIMARY>/SKILL.md` and follow its task-specific instructions. 5. Resolve tools only through the generated `skills/tool-index.md`; do not register MCP servers or install tools unless the user requested that action. If the repository is not the current workspace and no local repository path was supplied, explain that this adapter does not bundle a second copy of the router. Ask the user to open or clone `https://github.com/zhaoxuya520/reverse-skill` and then continue from its `RULES.md`. Do not treat the presence of this plugin, a target name, or a sample path as authorization. Authorization comes from the repository's scope contract.
GitHubで見る