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 gjoranv/claude-plan-skills --skill gh-read-plangit clone --depth 1 https://github.com/gjoranv/claude-plan-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/gjoranv/claude-plan-skills/gh-read-plan)<a href="https://agentmods.dev/skills/gjoranv/claude-plan-skills/gh-read-plan"><img src="https://agentmods.dev/badge/skills/gjoranv/claude-plan-skills/gh-read-plan/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/gjoranv/claude-plan-skills/gh-read-plan"><img src="https://agentmods.dev/badge/skills/gjoranv/claude-plan-skills/gh-read-plan.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.00034 | $0.00317 |
| Opus 5 | $0.00017 | $0.00159 |
| Sonnet 5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
gh-read-plan 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 11d 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
Read the GitHub issue in $ARGUMENTS (issue URL or owner/repo#number) containing the detailed plan for the work that will be started or continued in this conversation.
When reading the issue, check both the body and comments for content. Steps may be in a separate Steps comment (new format) or in the issue body (old format). Check for:
- a list of steps (with checkboxes) -- in the body or a Steps comment
- a design section -- in the body or a Design comment
- a diagram -- in the body or a Diagram comment
- links to relevant documentation, code, resources, and related issues
- a list of prerequisites, and if so, ask the user if those have been completed
- a link to one or more pull requests -- if so, read their diffs to understand what has already been implemented
Try to verify, from the comments and pull requests, which steps have been completed, and which are still pending.
If a durable-memory CLI is configured, query it with the issue's distinctive terms after reading. See the memory tool's own integration doc for mechanics.
Tell the user what you have learned from reading the issue, and ask any clarifying questions you may have about the work to be done.
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.
- 11d ago First seen · 24 lines · 34 tokens per session scan A 384af4dc4fc2
gh-read-plan is a skill published in the GitHub repository gjoranv/claude-plan-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 317 once invoked, about $0.0002 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-31.
Other skills, from other repositories
grill-me
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
prd-to-issues
A planning skill that turns an existing product requirements document, or PRD, into small GitHub Issues that developers can implement and verify. It groups work into complete user-facing slices instead of separate front-end, back-end, testing, and documentation tasks.
project-context-steward
A project-documentation skill that scans a new project or several related code repositories and records their shared context in a PROJECT_CONTEXT.md file. It captures the product, users, workflows, architecture, repository boundaries, terminology, entry points, and known pitfalls.
kelly-support
Personal App-in-Skill customer-support desk (help desk) that triages incoming support tickets from email, WhatsApp, web chat, contact forms, and WeChat, drafts KB-grounded replies, and proposes actions, then holds every send behind a human approval queue with a pre-send quality gate (support-qa) that outputs…