{"owner":"radareorg","repo":"radare2","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":2140,"categories":["root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"radare2":{"command":"npx","args":["-y","@modelcontextprotocol/server-radare2"]}}},"found":["AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"# Agentic Coding Guidelines for radare2\n\n## Work and references\n\nMake the smallest coherent fix. Reuse existing helpers; avoid unrelated cleanup,\nspeculative abstractions and repeated scans in hot paths. Extract helpers when\nthey simplify logic.\n\nSearch symbols and paths first; read only relevant sections:\n\n- APIs: `libr/include/` declarations, corresponding `libr/` implementations and callers. Verify signatures and ownership against current code.\n- Layout: libraries in `libr/`, CLI tools in `binr/`, plugins in `libr/*/p/`.\n- Style/build details: `DEVELOPERS.md` and `doc/indent-example.c`; public API/ABI changes: `doc/abi.md`.\n- Commands: `man/`, `r2 -h` and `<command>?`; test formats: `test/README.md` and nearby `test/db/` cases.\n\n## Style\n\n- Use descriptive function and variable names so code is readable without comments in most cases. Do not add multiline comments; use short single-line comments only for non-obvious intent.\n- Match nearby code: tabs, no trailing whitespace, braces even for single statements, and `case` labels aligned with `switch`.\n- Space before calls/control parentheses: `foo ()`, `if (x)`, `sizeof (int)`. Keep function signatures on one line without a space before `(`.\n- Initialize variables near first use; declare loop variables before `for`, not inside it.\n- Use `<r_types.h>` integer types (`ut8`, `ut32`, etc.), `PFMT64` formatting and `R_PACKED` for packed structures.\n- Do not run `clang-format-radare2` unless requested. `sys/lint.sh` provides style diagnostics for the whole tree; distinguish pre-existing findings.\n\n## Memory and APIs\n\n- Project convention omits NULL checks for small constant `R_NEW`/`R_NEW0` allocations.\n- Check runtime-sized allocations for failure; guard size arithmetic with `r_mul_overflow_*`/`r_add_overflow_*` before allocating. Check bounds before buffer access; endian helpers do not.\n- Never use `alloca` or variable-length stack arrays. Avoid NULL guards around `free` and destructors that accept NULL.\n- Use `R_RETURN_*` for public API preconditions; ordinary `if` for runtime/input errors. Use `r_util/r_assert.h` instead of `<assert.h>`.\n- Prefer `!strcmp ()`, `r_str_newf`, `r_str_pad` and endian helpers such as `r_read_le32`. Use `r_strbuf_*` for concatenation in loops to avoid repeated copying.\n- Use annotations from `libr/include/r_types.h` and `libr/include/r_types_null.h`; ownership macros are `R_OWNED`/`R_UNOWNED`.\n- Prefer `r_json_parsedup`; when borrowing buffers, follow the lifetime rules in `libr/include/r_util/r_json.h`.\n- New commands need `?` help. Use `R_LOG_*` for diagnostics and the existing console APIs for command output; remove debugging `eprintf` calls.\n\n## Build\n\n- For code changes, run `./configure` if needed, then `make -j2` from the root (adjust jobs to available resources). Keep failure output. Do not compile individual `.c`/`.o` files directly.\n- Run `sys/install.sh --without-pull` for a full clean rebuild and symlink installation.\n- `.d` files are compiler generated. If one causes a build failure, remove it and rebuild; do not edit it.\n- Edit `configure.acr` and regenerate `configure` with `acr`; do not edit generated `configure` directly.\n- Update both Make and Meson for library dependencies. Register new plugins in `dist/plugins-cfg/plugins.def.cfg`, `dist/plugins-cfg/plugins.static.cfg` and the relevant `libr/*/meson.build`.\n\n## Verify\n\n- Use `r2r` tests in `test/db/` for `r2` behavior and C unit tests in `test/unit/` for direct API behavior. Reuse test files and fixtures when suitable. Cover the reported behavior and edge cases; check expected output before changing it.\n- When writing r2r tests, avoid the need to create temporal files or execute system programs like '!!' or '| grep'\n- Build before running `r2r -C test db/...` from the root. Existing `symstall` symlinks use rebuilt files without reinstalling. Otherwise, install this checkout or set its executable, library and plugin paths. See [Regression testing](DEVELOPERS.md#regression-testing).\n- Keep the filename last in `r2` invocations. Use `-n` only for raw input: it skips binary loading. `io.va=false` changes addressing, not binary loading.\n- Binary fixtures belong in `radare2-testbins` (`test/bins/`), not this repository. `// R2R` comments can link source files to tests.\n- For memory debugging, see `DEVELOPERS.md` (Error diagnosis): `R2_DEBUG=1` and `sys/sanitize.sh`.\n- Run `git diff --check`; report what was tested and any blockers. Documentation-only changes need reference checks, not a full build.\n- Before reporting completion, inspect `git status --short` and the diff. Verify every requested deliverable exists and contains the required content; remove temporary artifacts you created.\n\n## Commits\n\nCommit only when requested or needed for a requested PR; otherwise suggest a one-line message.\nWrite a one-line subject starting with a capital letter. If a body is needed,\nseparate it with a blank line and use only short bullet points.\nFor user-visible changes, append one existing `##tag` as the final word of the\nsubject; security fixes use `##crash`. See [Commit messages](DEVELOPERS.md#commit-messages)\nfor details, issue references and the tag list.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"# Agentic Coding Guidelines for radare2\n\n## Work and references\n\nMake the smallest coherent fix. Reuse existing helpers; avoid unrelated cleanup,\nspeculative abstractions and repeated scans in hot paths. Extract helpers when\nthey simplify logic.\n\nSearch symbols and paths first; read only relevant sections:\n\n- APIs: `libr/include/` declarations, corresponding `libr/` implementations and callers. Verify signatures and ownership against current code.\n- Layout: libraries in `libr/`, CLI tools in `binr/`, plugins in `libr/*/p/`.\n- Style/build details: `DEVELOPERS.md` and `doc/indent-example.c`; public API/ABI changes: `doc/abi.md`.\n- Commands: `man/`, `r2 -h` and `<command>?`; test formats: `test/README.md` and nearby `test/db/` cases.\n\n## Style\n\n- Use descriptive function and variable names so code is readable without comments in most cases. Do not add multiline comments; use short single-line comments only for non-obvious intent.\n- Match nearby code: tabs, no trailing whitespace, braces even for single statements, and `case` labels aligned with `switch`.\n- Space before calls/control parentheses: `foo ()`, `if (x)`, `sizeof (int)`. Keep function signatures on one line without a space before `(`.\n- Initialize variables near first use; declare loop variables before `for`, not inside it.\n- Use `<r_types.h>` integer types (`ut8`, `ut32`, etc.), `PFMT64` formatting and `R_PACKED` for packed structures.\n- Do not run `clang-format-radare2` unless requested. `sys/lint.sh` provides style diagnostics for the whole tree; distinguish pre-existing findings.\n\n## Memory and APIs\n\n- Project convention omits NULL checks for small constant `R_NEW`/`R_NEW0` allocations.\n- Check runtime-sized allocations for failure; guard size arithmetic with `r_mul_overflow_*`/`r_add_overflow_*` before allocating. Check bounds before buffer access; endian helpers do not.\n- Never use `alloca` or variable-length stack arrays. Avoid NULL guards around `free` and destructors that accept NULL.\n- Use `R_RETURN_*` for public API preconditions; ordinary `if` for runtime/input errors. Use `r_util/r_assert.h` instead of `<assert.h>`.\n- Prefer `!strcmp ()`, `r_str_newf`, `r_str_pad` and endian helpers such as `r_read_le32`. Use `r_strbuf_*` for concatenation in loops to avoid repeated copying.\n- Use annotations from `libr/include/r_types.h` and `libr/include/r_types_null.h`; ownership macros are `R_OWNED`/`R_UNOWNED`.\n- Prefer `r_json_parsedup`; when borrowing buffers, follow the lifetime rules in `libr/include/r_util/r_json.h`.\n- New commands need `?` help. Use `R_LOG_*` for diagnostics and the existing console APIs for command output; remove debugging `eprintf` calls.\n\n## Build\n\n- For code changes, run `./configure` if needed, then `make -j2` from the root (adjust jobs to available resources). Keep failure output. Do not compile individual `.c`/`.o` files directly.\n- Run `sys/install.sh --without-pull` for a full clean rebuild and symlink installation.\n- `.d` files are compiler generated. If one causes a build failure, remove it and rebuild; do not edit it.\n- Edit `configure.acr` and regenerate `configure` with `acr`; do not edit generated `configure` directly.\n- Update both Make and Meson for library dependencies. Register new plugins in `dist/plugins-cfg/plugins.def.cfg`, `dist/plugins-cfg/plugins.static.cfg` and the relevant `libr/*/meson.build`.\n\n## Verify\n\n- Use `r2r` tests in `test/db/` for `r2` behavior and C unit tests in `test/unit/` for direct API behavior. Reuse test files and fixtures when suitable. Cover the reported behavior and edge cases; check expected output before changing it.\n- When writing r2r tests, avoid the need to create temporal files or execute system programs like '!!' or '| grep'\n- Build before running `r2r -C test db/...` from the root. Existing `symstall` symlinks use rebuilt files without reinstalling. Otherwise, install this checkout or set its executable, library and plugin paths. See [Regression testing](DEVELOPERS.md#regression-testing).\n- Keep the filename last in `r2` invocations. Use `-n` only for raw input: it skips binary loading. `io.va=false` changes addressing, not binary loading.\n- Binary fixtures belong in `radare2-testbins` (`test/bins/`), not this repository. `// R2R` comments can link source files to tests.\n- For memory debugging, see `DEVELOPERS.md` (Error diagnosis): `R2_DEBUG=1` and `sys/sanitize.sh`.\n- Run `git diff --check`; report what was tested and any blockers. Documentation-only changes need reference checks, not a full build.\n- Before reporting completion, inspect `git status --short` and the diff. Verify every requested deliverable exists and contains the required content; remove temporary artifacts you created.\n\n## Commits\n\nCommit only when requested or needed for a requested PR; otherwise suggest a one-line message.\nWrite a one-line subject starting with a capital letter. If a body is needed,\nseparate it with a blank line and use only short bullet points.\nFor user-visible changes, append one existing `##tag` as the final word of the\nsubject; security fixes use `##crash`. See [Commit messages](DEVELOPERS.md#commit-messages)\nfor details, issue references and the tag list.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/radareorg/radare2/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Agentic Coding Guidelines for radare2\n\n## Work and references\n\nMake the smallest coherent fix. Reuse existing helpers; avoid unrelated cleanup,\nspeculative abstractions and repeated scans in hot paths. Extract helpers when\nthey simplify logic.\n\nSearch symbols and paths first; read only relevant sections:\n\n- APIs: `libr/include/` declarations, corresponding `libr/` implementations and callers. Verify signatures and ownership against current code.\n- Layout: libraries in `libr/`, CLI tools in `binr/`, plugins in `libr/*/p/`.\n- Style/build details: `DEVELOPERS.md` and `doc/indent-example.c`; public API/ABI changes: `doc/abi.md`.\n- Commands: `man/`, `r2 -h` and `<command>?`; test formats: `test/README.md` and nearby `test/db/` cases.\n\n## Style\n\n- Use descriptive function and variable names so code is readable without comments in most cases. Do not add multiline comments; use short single-line comments only for non-obvious intent.\n- Match nearby code: tabs, no trailing whitespace, braces even for single statements, and `case` labels aligned with `switch`.\n- Space before calls/control parentheses: `foo ()`, `if (x)`, `sizeof (int)`. Keep function signatures on one line without a space before `(`.\n- Initialize variables near first use; declare loop variables before `for`, not inside it.\n- Use `<r_types.h>` integer types (`ut8`, `ut32`, etc.), `PFMT64` formatting and `R_PACKED` for packed structures.\n- Do not run `clang-format-radare2` unless requested. `sys/lint.sh` provides style diagnostics for the whole tree; distinguish pre-existing findings.\n\n## Memory and APIs\n\n- Project convention omits NULL checks for small constant `R_NEW`/`R_NEW0` allocations.\n- Check runtime-sized allocations for failure; guard size arithmetic with `r_mul_overflow_*`/`r_add_overflow_*` before allocating. Check bounds before buffer access; endian helpers do not.\n- Never use `alloca` or variable-length stack arrays. Avoid NULL guards around `free` and destructors that accept NULL.\n- Use `R_RETURN_*` for public API preconditions; ordinary `if` for runtime/input errors. Use `r_util/r_assert.h` instead of `<assert.h>`.\n- Prefer `!strcmp ()`, `r_str_newf`, `r_str_pad` and endian helpers such as `r_read_le32`. Use `r_strbuf_*` for concatenation in loops to avoid repeated copying.\n- Use annotations from `libr/include/r_types.h` and `libr/include/r_types_null.h`; ownership macros are `R_OWNED`/`R_UNOWNED`.\n- Prefer `r_json_parsedup`; when borrowing buffers, follow the lifetime rules in `libr/include/r_util/r_json.h`.\n- New commands need `?` help. Use `R_LOG_*` for diagnostics and the existing console APIs for command output; remove debugging `eprintf` calls.\n\n## Build\n\n- For code changes, run `./configure` if needed, then `make -j2` from the root (adjust jobs to available resources). Keep failure output. Do not compile individual `.c`/`.o` files directly.\n- Run `sys/install.sh --without-pull` for a full clean rebuild and symlink installation.\n- `.d` files are compiler generated. If one causes a build failure, remove it and rebuild; do not edit it.\n- Edit `configure.acr` and regenerate `configure` with `acr`; do not edit generated `configure` directly.\n- Update both Make and Meson for library dependencies. Register new plugins in `dist/plugins-cfg/plugins.def.cfg`, `dist/plugins-cfg/plugins.static.cfg` and the relevant `libr/*/meson.build`.\n\n## Verify\n\n- Use `r2r` tests in `test/db/` for `r2` behavior and C unit tests in `test/unit/` for direct API behavior. Reuse test files and fixtures when suitable. Cover the reported behavior and edge cases; check expected output before changing it.\n- When writing r2r tests, avoid the need to create temporal files or execute system programs like '!!' or '| grep'\n- Build before running `r2r -C test db/...` from the root. Existing `symstall` symlinks use rebuilt files without reinstalling. Otherwise, install this checkout or set its executable, library and plugin paths. See [Regression testing](DEVELOPERS.md#regression-testing).\n- Keep the filename last in `r2` invocations. Use `-n` only for raw input: it skips binary loading. `io.va=false` changes addressing, not binary loading.\n- Binary fixtures belong in `radare2-testbins` (`test/bins/`), not this repository. `// R2R` comments can link source files to tests.\n- For memory debugging, see `DEVELOPERS.md` (Error diagnosis): `R2_DEBUG=1` and `sys/sanitize.sh`.\n- Run `git diff --check`; report what was tested and any blockers. Documentation-only changes need reference checks, not a full build.\n- Before reporting completion, inspect `git status --short` and the diff. Verify every requested deliverable exists and contains the required content; remove temporary artifacts you created.\n\n## Commits\n\nCommit only when requested or needed for a requested PR; otherwise suggest a one-line message.\nWrite a one-line subject starting with a capital letter. If a body is needed,\nseparate it with a blank line and use only short bullet points.\nFor user-visible changes, append one existing `##tag` as the final word of the\nsubject; security fixes use `##crash`. See [Commit messages](DEVELOPERS.md#commit-messages)\nfor details, issue references and the tag list.\n","isInternal":false,"tokens":1240,"sizeBytes":5182},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":196},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":182},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/radareorg/radare2/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":175}],"systemPromptSnippet":"<yakaai_skills repo=\"radareorg/radare2\">\n<!-- File: AGENTS.md (Tokens: ~1240 | Category: root-instruction) -->\n# Agentic Coding Guidelines for radare2\n\n## Work and references\n\nMake the smallest coherent fix. Reuse existing helpers; avoid unrelated cleanup,\nspeculative abstractions and repeated scans in hot paths. Extract helpers when\nthey simplify logic.\n\nSearch symbols and paths first; read only relevant sections:\n\n- APIs: `libr/include/` declarations, corresponding `libr/` implementations and callers. Verify signatures and ownership against current code.\n- Layout: libraries in `libr/`, CLI tools in `binr/`, plugins in `libr/*/p/`.\n- Style/build details: `DEVELOPERS.md` and `doc/indent-example.c`; public API/ABI changes: `doc/abi.md`.\n- Commands: `man/`, `r2 -h` and `<command>?`; test formats: `test/README.md` and nearby `test/db/` cases.\n\n## Style\n\n- Use descriptive function and variable names so code is readable without comments in most cases. Do not add multiline comments; use short single-line comments only for non-obvious intent.\n- Match nearby code: tabs, no trailing whitespace, braces even for single statements, and `case` labels aligned with `switch`.\n- Space before calls/control parentheses: `foo ()`, `if (x)`, `sizeof (int)`. Keep function signatures on one line without a space before `(`.\n- Initialize variables near first use; declare loop variables before `for`, not inside it.\n- Use `<r_types.h>` integer types (`ut8`, `ut32`, etc.), `PFMT64` formatting and `R_PACKED` for packed structures.\n- Do not run `clang-format-radare2` unless requested. `sys/lint.sh` provides style diagnostics for the whole tree; distinguish pre-existing findings.\n\n## Memory and APIs\n\n- Project convention omits NULL checks for small constant `R_NEW`/`R_NEW0` allocations.\n- Check runtime-sized allocations for failure; guard size arithmetic with `r_mul_overflow_*`/`r_add_overflow_*` before allocating. Check bounds before buffer access; endian helpers do not.\n- Never use `alloca` or variable-length stack arrays. Avoid NULL guards around `free` and destructors that accept NULL.\n- Use `R_RETURN_*` for public API preconditions; ordinary `if` for runtime/input errors. Use `r_util/r_assert.h` instead of `<assert.h>`.\n- Prefer `!strcmp ()`, `r_str_newf`, `r_str_pad` and endian helpers such as `r_read_le32`. Use `r_strbuf_*` for concatenation in loops to avoid repeated copying.\n- Use annotations from `libr/include/r_types.h` and `libr/include/r_types_null.h`; ownership macros are `R_OWNED`/`R_UNOWNED`.\n- Prefer `r_json_parsedup`; when borrowing buffers, follow the lifetime rules in `libr/include/r_util/r_json.h`.\n- New commands need `?` help. Use `R_LOG_*` for diagnostics and the existing console APIs for command output; remove debugging `eprintf` calls.\n\n## Build\n\n- For code changes, run `./configure` if needed, then `make -j2` from the root (adjust jobs to available resources). Keep failure output. Do not compile individual `.c`/`.o` files directly.\n- Run `sys/install.sh --without-pull` for a full clean rebuild and symlink installation.\n- `.d` files are compiler generated. If one causes a build failure, remove it and rebuild; do not edit it.\n- Edit `configure.acr` and regenerate `configure` with `acr`; do not edit generated `configure` directly.\n- Update both Make and Meson for library dependencies. Register new plugins in `dist/plugins-cfg/plugins.def.cfg`, `dist/plugins-cfg/plugins.static.cfg` and the relevant `libr/*/meson.build`.\n\n## Verify\n\n- Use `r2r` tests in `test/db/` for `r2` behavior and C unit tests in `test/unit/` for direct API behavior. Reuse test files and fixtures when suitable. Cover the reported behavior and edge cases; check expected output before changing it.\n- When writing r2r tests, avoid the need to create temporal files or execute system programs like '!!' or '| grep'\n- Build before running `r2r -C test db/...` from the root. Existing `symstall` symlinks use rebuilt files without reinstalling. Otherwise, install this checkout or set its executable, library and plugin paths. See [Regression testing](DEVELOPERS.md#regression-testing).\n- Keep the filename last in `r2` invocations. Use `-n` only for raw input: it skips binary loading. `io.va=false` changes addressing, not binary loading.\n- Binary fixtures belong in `radare2-testbins` (`test/bins/`), not this repository. `// R2R` comments can link source files to tests.\n- For memory debugging, see `DEVELOPERS.md` (Error diagnosis): `R2_DEBUG=1` and `sys/sanitize.sh`.\n- Run `git diff --check`; report what was tested and any blockers. Documentation-only changes need reference checks, not a full build.\n- Before reporting completion, inspect `git status --short` and the diff. Verify every requested deliverable exists and contains the required content; remove temporary artifacts you created.\n\n## Commits\n\nCommit only when requested or needed for a requested PR; otherwise suggest a one-line message.\nWrite a one-line subject starting with a capital letter. If a body is needed,\nseparate it with a blank line and use only short bullet points.\nFor user-visible changes, append one existing `##tag` as the final word of the\nsubject; security fixes use `##crash`. See [Commit messages](DEVELOPERS.md#commit-messages)\nfor details, issue references and the tag list.\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/radareorg/radare2/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}