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.
npx agentmods add commands/marcosd4h/deepextractruntime/rpcgit clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntimeWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01848 |
| Opus 5 | $0.00000 | $0.00924 |
| Sonnet 5 | $0.00000 | $0.00370 |
| Haiku 4.5 | $0.00000 | $0.00185 |
Grade A, and why
rpc 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 3d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RPC Analysis
Overview
Analyze RPC interfaces in Windows binaries using ground-truth NtApiDotNet extraction data. Enumerates interfaces, maps the RPC attack surface, audits security properties, and traces handler call chains.
The text after /rpc is the module name and optional subcommand (e.g., /rpc appinfo.dll, /rpc surface, /rpc audit appinfo.dll).
Subcommands
| Subcommand | Usage | Purpose |
|---|---|---|
| (default) | /rpc <module> |
Enumerate all RPC interfaces, procedures, endpoints |
workspace |
/rpc workspace |
Discover which workspace modules implement RPC interfaces |
surface |
/rpc surface [module] |
Risk-ranked RPC attack surface (module or system-wide) |
audit |
/rpc audit <module> |
RPC-specific security audit |
trace |
/rpc trace <module> <function> |
Trace RPC handler data flow to sinks |
clients |
/rpc clients <uuid> |
Find modules implementing/consuming a UUID |
topology |
/rpc topology [module] |
System-wide or per-module RPC client-server topology |
blast-radius |
/rpc blast-radius <module or uuid> |
Show co-hosted interface impact analysis |
stubs |
/rpc stubs <uuid> |
Show C# stub parameter signatures for an interface |
IMPORTANT: Execution Model
This is an execute-immediately command. Do NOT present anything for user confirmation. Run the requested analysis and present the report directly.
Execution Context
IMPORTANT: Skill script invocations like
python .claude/skills/.../script.pycan be run from the workspace root because those scripts manage their own path setup.
Steps
Step 0: Preflight Validation
Parse the subcommand and arguments:
- No subcommand + module name -> enumerate interfaces (default)
surface+ optional module -> attack surface rankingaudit+ module -> security audit (requires DB path)trace+ module + function -> handler chain trace (requires DB path)clients+ UUID -> find modules for interfacetopology+ optional module -> RPC client-server topology (system-wide or per-module)blast-radius+ module or UUID -> co-hosted interface impact analysisstubs+ UUID -> C# stub parameter signatures for interface
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.
- 3d ago First seen · 190 lines · 0 tokens per session scan A 82e5fc573bf9
rpc is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,848 tokens. 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.