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.
git clone --depth 1 https://github.com/OXI-717/ai-native-toolkitWrote 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/plugins/oxi-717/ai-native-toolkit/screencast)<a href="https://agentmods.dev/plugins/oxi-717/ai-native-toolkit/screencast"><img src="https://agentmods.dev/badge/plugins/oxi-717/ai-native-toolkit/screencast/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/plugins/oxi-717/ai-native-toolkit/screencast"><img src="https://agentmods.dev/badge/plugins/oxi-717/ai-native-toolkit/screencast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
screencast 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
{
"name": "screencast",
"description": "Record a demo video of a web-app flow: browser chrome, synthetic cursor, captions, mp4 from a declarative YAML scenario",
"source": "./plugins/screencast/",
"version": "0.1.2",
"author": {
"name": "OXI-717"
}
}What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 168 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#screencast 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 Changed 89d1a05cd17a
- 2mo ago First seen · 9 lines scan A a41e29ac488f
screencast is a plugin published in the GitHub repository OXI-717/ai-native-toolkit (9 stars, last pushed 29d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
review-squad
Multi-angle project review covering expert audits, visitor comprehension testing, task-completion smoke tests, and adversarial nitpick passes. Use when you want a thorough pre-launch review or a targeted quality check from any angle.
electron-playwright-validator
Electron app UI automation and validation via Playwright CDP.
redline
Human-in-the-loop review interface for Claude Code - request structured feedback on plans, PRs, and implementations via browser UI.
umb-cms-reviews
Skills for classifying, setting up, testing, and cleaning up Umbraco CMS pull requests using browser automation.
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
pedantic-coder
Zero-tolerance code pedantry — naming precision, casing law, structural symmetry, import discipline, and the obsessive details that separate clean code from correct code.