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.
/plugin marketplace add richawo/yaps-codex-pluginnpx agentmods add plugins/richawo/yaps-codex-plugin/yaps-transcriptiongit clone --depth 1 https://github.com/richawo/yaps-codex-pluginGrade A, and why
yaps-transcription 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.
What it actually says
{
"name": "yaps-transcription",
"displayName": "Yaps Transcription",
"version": "0.1.12",
"description": "Transcribe audio and video files into clean text with Yaps.",
"author": {
"name": "Yaps AI",
"email": "[email protected]",
"url": "https://www.yaps.ai"
},
"homepage": "https://www.yaps.ai",
"repository": "https://github.com/richawo/yaps-plugins",
"license": "MIT",
"keywords": [
"transcription",
"audio-to-text",
"video-to-text",
"speech-to-text"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 90 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 21 lines scan A 422d17ba8879
yaps-transcription is a plugin published in the GitHub repository richawo/yaps-codex-plugin (2 stars, last pushed 5d 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-08-31.
Other plugins, from other repositories
pad
Talk to your project. Pad is local-first project management for developers and AI agents — this plugin gives Claude Code a conversational Pad skill, typed shortcuts (/pad:status, /pad:capture, /pad:onboard, /pad:connect, /pad:disconnect), and consent-gated live item-change notifications.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
cortex
Remembers your decisions, coding conventions, and debugging lessons across every Claude Code session. Persistent local memory for AI coding agents.
lians
Bitemporal memory for Claude Code with deterministic supersession, point-in-time recall, local MCP, erasure proofs, and tamper-evident history.
brana
AI development system — skills, agents, and hooks for systematic software engineering with Claude Code.
promptline
Local, read-only visual timeline of your Claude Code prompt history - dashboard, activity heatmap, and searchable per-project/session feed. Binds to 127.0.0.1 only, no outbound network calls, nothing written back to /.claude.