skills.rest
warterbili
warterbiliCOMMUNITY
Explore all skills by this author →
Website𝕏@lsdwaterbiliGitHub

jsrpc-universal

Invoke JavaScript or native algorithms in browsers and Android via RPC frameworks.

Updated Aug 27, 2026
Search Tags:#rpc#reverse engineering#frida#jsrpc#sekiro#algorithm invocation#browser injection
One-click install
npx skills add https://github.com/warterbili/AUTO_REVERSE --skill jsrpc-universal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jsrpc-universal
Source: https://github.com/warterbili/AUTO_REVERSE/tree/main/skills/web/jsrpc-universal
Command: npx skills add https://github.com/warterbili/AUTO_REVERSE --skill jsrpc-universal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reverse engineering complex, obfuscated, or environment-dependent algorithms often requires extracting source code, mocking runtime environments (such as browser DOM or native app contexts), or reimplementing logic from scratch — all of which are time-consuming, fragile, and break when the target algorithm updates. This Skill eliminates that overhead by letting you invoke the target algorithm directly in its original running environment via RPC.

Core Features & Use Cases

  • Dual-framework support: Natively supports jxhczhl/JsRpc (lightweight, browser-focused RPC) and yint-tech/sekiro-open (production-grade cross-platform RPC for web and Android) to fit different project scale and platform requirements.
  • Multi-platform injection guidance: Covers injection methods for browser targets (console, Tampermonkey) and Android targets (Frida, Xposed), with recommendations for selecting the right approach based on anti-debugging strength and stability needs.
  • Workflow decision support: Provides a clear comparison of JsRpc vs pure algorithm reimplementation vs node environment mocking, so you can choose the most efficient path for your specific use case.
  • Operational best practices: Includes guidance on client routing, concurrency scaling, timeout troubleshooting, and security configuration to avoid common pitfalls like endpoint exposure or request mismatches.

Quick Start

Use the jsrpc-universal skill to remotely invoke a target site's request signing algorithm via RPC without extracting or reimplementing its source code.

Frequently Asked Questions about jsrpc-universal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I invoke an obfuscated algorithm remotely without extracting or reimplementing the source code?▼

You can invoke an obfuscated algorithm remotely by using RPC frameworks to call JavaScript or native functions directly within their original running environment, eliminating the need to extract, mock, or reimplement source code.

Does jsrpc-universal work with Frida for Android reverse engineering?▼

Yes, jsrpc-universal works with Frida for Android reverse engineering by providing multi-platform injection guidance for native app contexts, specifically supporting the yint-tech/sekiro-open framework for cross-platform Android targets.

What is the best way to call a browser signing algorithm without node environment mocking?▼

The best way to call a browser signing algorithm without node environment mocking is using the jxhczhl/JsRpc framework, which enables lightweight browser-focused RPC injection via console or Tampermonkey to execute the target function directly.

Can I use RPC for logged-in session workflows in CTF challenges?▼

Yes, you can use RPC for logged-in session workflows in CTF challenges because the remote invocation technique executes target algorithm functions within real browser or Android application environments, preserving authenticated session states.

JsRpc vs pure algorithm reimplementation: when should I choose remote invocation?▼

You should choose remote invocation over pure algorithm reimplementation when dealing with environment-dependent cryptographic logic or frequently updated target algorithms, as extracting code is fragile and breaks when the target updates.

Why does RPC request mismatch or endpoint exposure happen during concurrency scaling?▼

RPC request mismatch or endpoint exposure during concurrency scaling typically happens due to misconfigured client routing, unoptimized timeout thresholds, or missing security configurations, which can be resolved by following operational best practices.

Related Skills

Explore More Software Engineering Skills→
vzcovzco
15

trace-callers

Trace reverse call chains to reveal direct and indirect callers of a target function.

Official
Advanced
kiwamizamuraikiwamizamurai
7

writeup-generator

Generate CTF challenge writeups as README.md files using templates/writeup.md.

Community
Advanced
BrownFineSecurityBrownFineSecurity
811

jadx

Decompile Android APK DEX bytecode into readable Java source code.

Official
Advanced
zhizhuodemaozhizhuodemao
402

ast-deobfuscate

Deobfuscate JavaScript code using a Babel-based AST transformation pipeline.

Community
Advanced