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/7xmohamed/kata/readnpx skills add 7xmohamed/Kata --skill readgit clone --depth 1 https://github.com/7xmohamed/KataWrote 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/7xmohamed/kata/read)<a href="https://agentmods.dev/skills/7xmohamed/kata/read"><img src="https://agentmods.dev/badge/skills/7xmohamed/kata/read.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.00057 | $0.00923 |
| Opus 5 | $0.00028 | $0.00462 |
| Sonnet 5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
read 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 4d 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.
2. Create `~/Downloads/{title}-images/` and curl each URL in parallel (`&` + `wait`). Use the same proxy env vars as the fetch step. How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read: Fetch the Ground Truth
Prefix your first line with ⚔️ inline, not as its own paragraph.
Convert any URL or local PDF to clean Markdown and save it. No analysis, no summary, no discussion of the content unless explicitly asked.
Routing
| Input | Method |
|---|---|
.pdf URL or local PDF path |
PDF extraction |
GitHub URLs (github.com, raw.githubusercontent.com) |
Prefer raw content or gh first. Use the proxy cascade only as fallback. |
x.com, twitter.com |
Proxy cascade (r.jina.ai keeps image URLs). Do not try WebFetch; it 402s. |
| Everything else | Proxy cascade |
After routing, load references/read-methods.md and run the commands for the chosen method.
Output Format
Title: {title}
Author: {author} (if available)
Source: {platform}
URL: {original url}
Content
{full Markdown, truncated at 200 lines if long}
Saving
Save to ~/Downloads/{title}.md with YAML frontmatter by default.
Skip only if user says "just preview" or "don't save". Tell the user the saved path.
If ~/Downloads/{title}.md already exists, append -1, -2, etc., to the filename. Never overwrite an existing file without explicit confirmation.
Images
By default only save Markdown. Download images only when the user explicitly asks: "download images" or "save images".
When asked, after saving the Markdown:
- Extract image URLs:
grep -oE 'https?://[^ )"]+\.(jpg|jpeg|png|webp|gif)' {md_path} | sort -u - Create
~/Downloads/{title}-images/and curl each URL in parallel (&+wait). Use the same proxy env vars as the fetch step. - Report the count and folder path. If any download fails, list the failed URLs.
Hard Rules
- Do not summarize or analyze the content. Your job is conversion and storage, not interpretation.
- Never overwrite without confirmation. If the target filename already exists, use an auto-incremented suffix.
- Stop after the save report. Do not suggest follow-up actions unless the user asks.
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.
- 4d ago First seen · 85 lines · 57 tokens per session scan A 1f9f6680b6ff
read is a skill published in the GitHub repository 7xmohamed/Kata (2 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 923 once invoked, about $0.0003 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-31.
Other skills, from other repositories
maket-review
Review and fix Maket documents — audit HTML quality, charte compliance, image paths, layout issues, and automatically apply corrections with makethtml patch. Use this skill when the user says "review", "check", "fix", "audit", "correct", "improve" a document, or when they report visual problems like broken images…
maket
Orientation skill for Maket visual document work. Use when the user asks Claude to design, edit, review, or learn Maket; call maketlearn first for live product guidance, then operate through MCP tools.
a11y-grid
Guides accessible data grid, interactive table, and sortable table implementation. Auto-invokes when creating data grids, spreadsheet interfaces, sortable tables, or interactive table cells. Critical distinction — most data tables do NOT need role="grid". Covers table vs grid decision, HTML table accessibility…
book-serif-index
Create an archival book-reader design system with serif-led pages, mono index navigation, aged paper surfaces, margin notes, and a premium catalog frame.
editing
PPT 模板编辑指南 — 用于以现有演示文稿为模板进行内容替换和布局优化。当用户需要编辑/修改已有 PPTX 时触发。.
spec-interview
Conducts a deep, multi-round interview to clarify ambiguous requirements and produces a structured specification document. Automatically discovers requirement files and asks probing, non-obvious questions across technical implementation, UX/UI, trade-offs, edge cases, and architectural decisions.