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-accessibility-testingnpx skills add ShaftHQ/SHAFT_ENGINE --skill shaft-accessibility-testinggit 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-accessibility-testing)<a href="https://agentmods.dev/skills/shafthq/shaft_engine/shaft-accessibility-testing"><img src="https://agentmods.dev/badge/skills/shafthq/shaft_engine/shaft-accessibility-testing.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.00031 | $0.00075 |
| Opus 5 | $0.00015 | $0.00037 |
| Sonnet 5 | $0.00006 | $0.00015 |
| Haiku 4.5 | $0.00003 | $0.00007 |
Grade A, and why
shaft-accessibility-testing 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 Accessibility Testing
Start with shaft-developer, then read and follow the accessibility-testing 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 · 9 lines · 31 tokens per session scan A 7e050234062f
shaft-accessibility-testing is a skill published in the GitHub repository ShaftHQ/SHAFT_ENGINE (407 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 75 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
simulator-workflow
Build, run, and test iOS apps on simulators. Use when working on simulator build flows, app bundle discovery, simulator resolution, or boot/install/launch logic.
visual-check
Record and check iOS and Android UI flows with uiagent.py (cloud) or uiagentlocal.py (Ollama). Use when recording a visual baseline, running check or check-all, debugging simulator taps, or editing files under visual-testing/.
e2e
Run or author a Maestro E2E flow on an iOS simulator. Usage: /podium-mcp:e2e [ ].
xcforge
Complete reference for xcforge — 109 MCP tools + 113 CLI commands for iOS development. Covers build, test, simulator, physical devices, SPM, UI automation, screenshots, logs, git, visual regression, accessibility, localization, session profiles, diagnosis workflows, plan execution, LLDB debugger integration, bless…
scrcpy-mcp
Professional Android automation agent for device interaction, UI testing, and app management. Use for: (1) interacting with Android apps, (2) filling inputs, (3) structural UI inspection via XML/axtree, (4) complex multi-step mobile tasks. Prefer XML/axtree over screenshots — images are expensive tokens.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.