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/hacklyc/myagents/myagents-speech-recognitionnpx skills add hAcKlyc/MyAgents --skill myagents-speech-recognitiongit clone --depth 1 https://github.com/hAcKlyc/MyAgentsWrote 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/hacklyc/myagents/myagents-speech-recognition)<a href="https://agentmods.dev/skills/hacklyc/myagents/myagents-speech-recognition"><img src="https://agentmods.dev/badge/skills/hacklyc/myagents/myagents-speech-recognition.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 | $0.00112 | $0.00833 |
| Opus 5 | $0.00056 | $0.00417 |
| Sonnet 5 | $0.00022 | $0.00167 |
| Haiku 4.5 | $0.00011 | $0.00083 |
Grade A, and why
myagents-speech-recognition 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 5d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 5d ago First seen · 59 lines · 112 tokens per session scan A 8f9f4d9b43e0
myagents-speech-recognition is a skill published in the GitHub repository hAcKlyc/MyAgents (865 stars, last pushed yesterday), licensed AGPL-3.0. It adds 112 tokens to every session and 833 once invoked, about $0.0006 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
aptabase-analytics-report
Export and analyze Vibe Aptabase analytics for recent time windows or existing CSV exports, with emphasis on failure rates, affected users, app versions, and OS breakdowns. Use when Codex needs to: (1) export recent analytics with scripts/exportanalytics.py, (2) filter an export to the exact last N hours, (3) restrict…
github-wake
Register an existing GitHub issue so the current Codex or Claude Code session is woken when its first future comment arrives. Use when work is genuinely blocked on a GitHub reply and the session must resume asynchronously.
code-walk-thru
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is…
log-work
Log the work segment that you did after the last work log until now in a.
release
Prepare, validate, and publish a Pake release. Not for version bumps without release intent.
pake
Package any website or local web build into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website or a local dist/ folder, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or…