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 skills/shafthq/shaft_engine/shaft-recording-codegennpx skills add ShaftHQ/SHAFT_ENGINE --skill shaft-recording-codegengit clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINEWrote 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/shafthq/shaft_engine/shaft-recording-codegen)<a href="https://agentmods.dev/skills/shafthq/shaft_engine/shaft-recording-codegen"><img src="https://agentmods.dev/badge/skills/shafthq/shaft_engine/shaft-recording-codegen.svg" alt="Measured on agentmods" 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.00035 | $0.00082 |
| Opus 5 | $0.00017 | $0.00041 |
| Sonnet 5 | $0.00007 | $0.00016 |
| Haiku 4.5 | $0.00003 | $0.00008 |
Grade A, and why
shaft-recording-codegen 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 6d 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
SHAFT Recording Codegen
Start with SHAFT Developer, then read and follow the recording-codegen playbook.
What ships with it
2 files 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.
- 6d ago First seen · 10 lines · 35 tokens per session scan A 591bc1ba978c
shaft-recording-codegen is a skill published in the GitHub repository ShaftHQ/SHAFT_ENGINE (408 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 82 once invoked, about $0.0002 per session on Opus 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
melaya-setup
Use for anything involving Melaya. Connecting for the first time; setting up phone or browser control; pairing a phone, installing the app, starting the local runner; driving an Android phone or a browser; building, validating, scheduling or debugging agent pipelines; reading connected services; diagnosing a failed…
mimic
Drive an android device from a shell with the mimic cli -- read the on-screen accessibility tree (filtered/queried on-device to stay small) and tap, swipe, click, type, scroll, and navigate. Use for ui automation on a connected/termux android device. Covers setup, every subcommand, and how to keep agent context small.
upgrade-browser
Upgrade browser versions (Chrome or Firefox) in the Flutter Web Engine and/or Framework tests. Use when asked to roll or upgrade Chrome or Firefox to a newer version.
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
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…