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 skills add hachiwar/codex-skills --skill claude-fix-unicode-decodegit clone --depth 1 https://github.com/hachiwar/codex-skillsWrote 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/hachiwar/codex-skills/claude-fix-unicode-decode)<a href="https://agentmods.dev/skills/hachiwar/codex-skills/claude-fix-unicode-decode"><img src="https://agentmods.dev/badge/skills/hachiwar/codex-skills/claude-fix-unicode-decode.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.00116 | $0.00937 |
| Opus 5 | $0.00058 | $0.00468 |
| Sonnet 5 | $0.00023 | $0.00187 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
claude-fix-unicode-decode 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 67 lines · 116 tokens per session scan A 4f8877ff2344
claude-fix-unicode-decode is a skill published in the GitHub repository hachiwar/codex-skills (2 stars, last pushed 2mo ago), with no licence file. It adds 116 tokens to every session and 937 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
root-cause-analysis
Produce a systemic, evidence-based incident RCA/postmortem after a failure: timeline, causal chain, contributing conditions, corrective actions, and prevention. Use when recurrence prevention and organizational learning are primary. Do not use as a generic live debugger.
debugging
Investigate and safely fix an active, observable software failure, error, regression, or unexpected behavior using reproduction and evidence. Use for the proximate technical cause and remediation. Do not use for a systemic incident postmortem or general performance tuning without a failure.
performance-optimization
Measure, diagnose, and improve a performance or capacity objective?latency, throughput, CPU, memory, scalability, or cost?without regressing correctness. Use when performance is the primary requested outcome. Do not use for generic code cleanup or an unmeasured incident postmortem.
query-loki-project-logs
Query Grafana Loki logs that are organized by labels such as projectname or project, env, and filename, where filename distinguishes nginx, web, worker, stdout, and stderr streams. Use when Codex needs to inspect logs with logcli, discover available projects or environments, list a project's log files, narrow to a…