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 skills add batteryshark/rekit --skill exec-observegit clone --depth 1 https://github.com/batteryshark/rekitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/batteryshark/rekit/exec-observe)<a href="https://agentmods.dev/skills/batteryshark/rekit/exec-observe"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/exec-observe/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/batteryshark/rekit/exec-observe"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/exec-observe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00067 | $0.00407 |
| Opus 5.5 | $0.00027 | $0.00163 |
| Sonnet 5.5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
exec-observe 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 1mo 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.
What it actually says
Execute & Observe (dynamic)
⚡ Dynamic tier — this RUNS the target. Run it only where you don't mind the risk: a disposable VM or a dedicated analysis box, or behind an isolation provider.
When to use
Use this when you need the target's exit status, output, file effects, and timing. For
deeper visibility, use syscall-trace, net-capture, or frida-trace.
What it does
Runs the target in a fresh temp working directory with a timeout, and captures:
- exit code (and whether it timed out),
- stdout / stderr (head),
- wall-clock duration,
- files created in the working dir.
It bounds the run (working dir + timeout) but does not sandbox the target — the target can do anything the host allows.
Consent
Because it executes untrusted code, it's gated:
- via rekit:
rekit run --allow-dynamic exec-observe <target>(the dispatcher sets the consent env for the runner); - direct call: pass
--yes-i-consentor setREKIT_ALLOW_DYNAMIC=1.
Without consent it refuses with exit 4.
Usage
rekit run --allow-dynamic exec-observe ./sample --timeout 15
rekit run --allow-dynamic exec-observe ./sample --format json
Prerequisites
- python3 ≥ 3.8 — pure stdlib. (Whatever the target needs to run is on you.)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 46 lines · 67 tokens per session scan A 34d2222ac47b
exec-observe is a skill published in the GitHub repository batteryshark/rekit (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 407 once invoked, about $0.0003 per session on Opus 5.5. 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.