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 yamadashy/agent-readable --skill readable-githubgit clone --depth 1 https://github.com/yamadashy/agent-readableWrote 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/yamadashy/agent-readable/readable-github)<a href="https://agentmods.dev/skills/yamadashy/agent-readable/readable-github"><img src="https://agentmods.dev/badge/skills/yamadashy/agent-readable/readable-github/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yamadashy/agent-readable/readable-github"><img src="https://agentmods.dev/badge/skills/yamadashy/agent-readable/readable-github.svg" alt="Reviewed on agentmods" width="80" 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.00101 | $0.00506 |
| Opus 5.5 | $0.00040 | $0.00202 |
| Sonnet 5.5 | $0.00020 | $0.00101 |
| Haiku 4.5 | $0.00010 | $0.00051 |
Grade A, and why
readable-github 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 1mo 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
GitHub Reader
Uses the gh CLI (which calls the GitHub REST/GraphQL API) for everything. The CLI handles auth, pagination, and rate limiting; AUP exempts API access from its scraping clauses.
Prerequisite
gh auth status
If not logged in: gh auth login.
Pick the right reference
Identify what kind of GitHub URL the user supplied, then follow the matching reference file:
| URL shape | Reference |
|---|---|
github.com/{owner}/{repo} (root, README, file tree) |
references/repo.md |
github.com/{owner}/{repo}/issues/... |
references/issues.md |
github.com/{owner}/{repo}/pull/... |
references/pulls.md |
github.com/{owner}/{repo}/discussions/... |
references/discussions.md |
github.com/{owner}/{repo}/blob/..., tree/..., code search |
references/code.md |
github.com/{owner}/{repo}/releases/... |
references/releases.md |
For Gist URLs (gist.github.com/...), use the readable-gist skill instead.
General tips
- Prefer
ghsubcommands (gh repo,gh issue,gh pr, ...) where they exist; fall back togh apifor endpoints they don't cover. - Use
--json {fields}to keep responses small. Each subcommand documents its--jsonfield set; rungh {sub} view --helpto list them. - Rate limit: 5,000 req/hour for authenticated users.
gh api rate_limitreports current usage.
What ships with it
6 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.
- 1mo ago First seen · 38 lines · 101 tokens per session scan A 3501f0bffb0b
readable-github is a skill published in the GitHub repository yamadashy/agent-readable (4 stars, last pushed 5mo ago), licensed MIT. It adds 101 tokens to every session and 506 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
check
Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
factory-babysit-pr
Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.
factory-review-prs
Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.
comet-github-pr-review
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…