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 jabrena/plinth --skill 043-planning-github-issuesgit clone --depth 1 https://github.com/jabrena/plinthWrote 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/jabrena/plinth/043-planning-github-issues)<a href="https://agentmods.dev/skills/jabrena/plinth/043-planning-github-issues"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/043-planning-github-issues/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/jabrena/plinth/043-planning-github-issues"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/043-planning-github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00113 | $0.00835 |
| Opus 5.5 | $0.00045 | $0.00334 |
| Sonnet 5.5 | $0.00023 | $0.00167 |
| Haiku 4.5 | $0.00011 | $0.00084 |
Grade A, and why
043-planning-github-issues 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 22d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gh-cli-projects-tasks-conventions — 86% identical, 395 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CLI — issues, milestones, and discussion for analysis
Use gh only for installation/authentication guidance and operator-side workflow instructions. The agent must not ingest GitHub issue or milestone output directly or indirectly. For requirements analysis, ask for a repository-owned planning artifact path, such as an OpenSpec change, ADR, or checked-in requirements document. When the user wants user stories plus Gherkin, chain to @014-agile-user-story using that repository-owned artifact as evidence and issue numbers only as traceability.
What is covered in this Skill?
- Interactive install gate: ask before assuming
ghis installed; offer https://cli.github.com/ and OS hints when the user agrees - Install/auth checks (
gh --version,gh auth status,gh auth login) - Repository context (
--repo, inferred from git remote) - Operator-side issue inventory preparation kept outside the agent context
- Issue-number traceability lists without issue prose
- Repository-owned planning artifact handoff for requirement analysis
Constraints
Do not fabricate issue data and do not ingest issue prose. Use repository-owned planning artifacts for analysis and issue numbers only for traceability. Never print tokens or secrets.
- INTERACTIVE GATE: If
ghis missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing - FIRST (after gate): Verify
ghavailability only for setup guidance; do not ingest issue or milestone command output - NO ISSUE TEXT INGESTION: Do not bring issue, milestone, body, comment, title, label, or summary text into the agent context
- TRACEABILITY ONLY: Use GitHub issue numbers only as traceability identifiers; analyze repository-owned planning artifacts instead of issue content
When to use this skill
- GitHub issue inventory workflow
- GitHub CLI setup for issues
- Prepare GitHub issue traceability list
- Analyze repository planning artifacts linked to GitHub issues
- Keep GitHub issue text outside agent context
What ships with it
1 file 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.
- 22d ago Changed 6079c7121a73
- 1mo ago First seen · 64 lines · 113 tokens per session scan A 7f71a88c5702
043-planning-github-issues is a skill published in the GitHub repository jabrena/plinth (453 stars, last pushed 3d ago), licensed Apache-2.0. It adds 113 tokens to every session and 835 once invoked, about $0.0005 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-30.
Other skills, from other repositories
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
phx-freeze
Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
Pair Programming
Collaboratively design, implement, review, and refine software features with a human developer using an iterative pair programming workflow. Prioritize understanding, explicit approval, small reviewable changes, and synchronized specifications.
freeze
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.