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 commands/deapi-ai/claude-code-skills/transcribegit clone --depth 1 https://github.com/deapi-ai/claude-code-skillsWhat 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.00026 | $0.00562 |
| Opus 5 | $0.00013 | $0.00281 |
| Sonnet 5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
transcribe scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://api.deapi.ai/api/v1/client/vid2txt" \ What it actually says
Transcription via deAPI
Transcribe media from URL: $ARGUMENTS
Step 1: Determine endpoint
| URL type | Endpoint |
|---|---|
.mp3, .wav, .m4a, .flac, .ogg |
aud2txt |
YouTube, X, .mp4, .webm, other video |
vid2txt |
Step 2: Send request
For video:
curl -s -X POST "https://api.deapi.ai/api/v1/client/vid2txt" \
-H "Authorization: Bearer $DEAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"video_url": "$ARGUMENTS", "include_ts": true, "model": "WhisperLargeV3"}'
For audio:
curl -s -X POST "https://api.deapi.ai/api/v1/client/aud2txt" \
-H "Authorization: Bearer $DEAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"audio_url": "$ARGUMENTS", "include_ts": true, "model": "WhisperLargeV3"}'
Step 3: Poll status (feedback loop)
Extract request_id from response, then poll every 10 seconds:
curl -s "https://api.deapi.ai/api/v1/client/request-status/{request_id}" \
-H "Authorization: Bearer $DEAPI_API_KEY"
Status handling:
processing→ wait 10s, poll againdone→ proceed to Step 4failed→ report error message to user, STOP
Step 4: Fetch and present result
When status = "done", fetch content from result_url and present transcription in readable format with timestamps.
Step 5: Offer follow-up
Ask user: "Would you like me to summarize the main points?"
Error handling
| Error | Action |
|---|---|
| 401 Unauthorized | Check if $DEAPI_API_KEY is set correctly |
| 429 Rate Limited | Wait 60s and retry |
| 500 Server Error | Wait 30s and retry once |
| Invalid URL | Ask user to verify the URL format |
| Timeout (>5min) | Inform user, suggest trying shorter content |
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 · 67 lines · 26 tokens per session scan A b8c9ba85e4a7
transcribe is a command published in the GitHub repository deapi-ai/claude-code-skills (21 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 562 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
refactor
Suggest refactoring opportunities.
test-coverage
Analyze test coverage and suggest improvements.
test-e2e
Write end-to-end tests for critical user journeys.
test-integration
Write integration tests for component boundaries.
export
Design public API exports.
newpkg
Generate new package with Nx.